From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Roxborough To: Fernando Nasser Cc: insight@sources.redhat.com Subject: Re: Stack Window Problem [was: Re: DLLs and Insight...] Date: Wed, 31 Oct 2001 11:33:00 -0000 Message-id: <3BE054E0.9EAA172@redhat.com> References: <3BD5A9E0.F58D0D66@redhat.com> <20011023140707.D23357@redhat.com> <3BE036A6.DBBBB5E2@redhat.com> <3BE04753.4AA1A1B9@redhat.com> X-SW-Source: 2001-q4/msg00241.html Fernando Nasser wrote: > > Ian Roxborough wrote: > > > > Hi, > > > > so I'm still slogging away at the Windows crashing problem and > > then I had the problem where I couldn't see the source of the Tk > > DLL again. > > > > Problem: I'm running Insight and Tk segfaults (which I what I want), > > but when I look at the stack all I see are "????" where I should > > see Tk functions. I can set breakpoints in Tk functions (which don't > > work), I can browse Tk functions in the Function Browser, but can't > > see them in drop down comboboxes in the Source Window. > > > > It seems to me that this is and intermittent problem with Insight. > > I checked it against at pre-Tcl8.3 Insight build and could see > > all the stack entries without any problem. > > > > This is a common symptom of stack corruption as well. What does the > command like "bt" command shows? (try it in the console window, > I don't think it matters not being in the real console). bt shows the same as the Insight stack window, i.e. stack frames inside the Tk DLL are shown as "??". Running gdb using the "-nw" flags gives the same results. If it is stack corruption, would it be normal to vary between similar versions of gdb? Ian.