Re: Crash with xemacs 21.4.4
Andy Piper <andyp(a)bea.com> wrote:
Right, but which Motif call. Maybe we could just not make the call -
sure
we might get a leak but doesn't seem so bad for delete_device()
I'm not sure it's that simple, as the "offending function" is
XtDestroyWidget(). I've attached a purify fragment that describes
what's happening. Two things to note, though:
1. Purify stack traces are inverted. Most-recently-called functions are
at the top.
2. This is for XEmacs 21.4.4. Line numbers might be occasionally off,
as I was trying to tweak the code to further characterize this bug.
Basically, all of the problems are being caused by internal Motif code,
deep in the bowels.
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
Attachments:
- purify-info.ksh (text/plain — 3.4 KB)