🚀 go-pugleaf

Has anyone else seen a situation where phase 2 of XtDestroy seg faults
if more than 1 popup dialog was destroyed during a callback? If so,
what's the scoop? 

The stack traces are pretty wierd...somehow XtCreateApplicationShell
is getting called during XtDoPhase2Destroy. See below for more
info...of course, the HP debugger isn't exactly known for being smart
about stack traces...this could be all garbage.

If it matters, I'm running HPUX-8.0, X11R4, Motif 1.1. 

Sorry if this is a FAQ, I couldn't find it in the list.

Email response preferable...I'll summarize if it seems useful.

Stack Trace:

 0 _XtCreateApplicationShell + 0x000001be (0x346630, 0xffeff750, 
	0xe4208, 0x3464d8, 0x346630)
 1 __XmNavigate + 0x000002ee (0xffeff6b8, 0x3464d8, 0x1, 0x2e134c, 0x6)
 2 __XtOnGrabList + 0x00000344 (0xffeff6b8, 0x346630, 0x19, 0x2, 0xffeff6f8) 
 3 _XtDispatchEvent + 0x00000032 (0xffeff6b8, 0x3464d8, 0xffeff724, 
	0x2e13d6, 0x2)
 4 __XmNavigate + 0x00000412 (0x3464d8, 0x346630, 0, 0, 0x2ecff8)
 5 __XtCallSmallCallbacks + 0x0000009c (0x3464d8, 0x3464ea, 
	0, 0xe20b6, 0xe20f6)
 6 _XtCreateApplicationShell + 0x00000134 (0x3464d8, 0x2, 0x1, 0,
	0xffeffbc4)
 7 __XtDoPhase2Destroy + 0x00000038 (0x2df118, 0x2, 0x2df118, 
	0x33a92, 0x2)
 8 _XtProcessEvent + 0x00000018 (0x3, 0, 0x4, 0x7, 0x2b521498)

Thanks much.
-- 
"When you're down, it's a long way up
 When you're up, it's a long way down
 It's all the same thing
 And it's no new tale to tell"                      ../ray\..