🚀 go-pugleaf

hi

perhaps a stupid question: 

     which are the side effects of the DPSTraceContext() function?

the answer could help me to solve a problem found in a programming session: 
my program (lets call it MyApp) is builded with InterfaceBuilder 2.1 under 
NeXTStep 2.0. 

MyApp wants to add some matrix elements to its mainmenu. therefore it
uses in a seperate routine called after the appDidBecomeActive: message
something like that:

	myMenu = [NXApp mainMenu]
	[myMenu sizeToFit]

this works fine when started without debugging. when debugging is done
with GDB there occurs a "Segmentation fault" in/after the sizeToFit:
call. the stackframe looks similar to this:

	#0 nxzonefreenolock()
	#1 free()
	#2 freeBuckets()
	...
	#5 NXHashInsert()
	#6 DPSMapNames()

bad. but there is a workaround for the problem. if i use DPSTraceContext()
in the following manner

	1) DPSTraceContext() YES after loading the *nib file and before
	[NXApp run]

	2) DPSTraceContext NO before launching the main routines of MyApp
	after receiving the appDidBecomeActive: message

the fault doesn't occure. "learning" from DPSTraceContext() could solve
the problem. another help would be the documentation for DPSMapNames()
- any idea where can i find this?

ciao
stefan

--

##############################################################################
Institut fuer Neue Materialien (INM) #  
Universitaet des Saarlandes, Geb. 43 # Phone: +49 681 302 5086
Stefan Brueck                        # E-Mail (Internet): brueck@inm.uni-sb.de
W-6600 Saarbruecken (Germany)        #
##############################################################################