From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fernando Nasser To: Ian Roxborough Cc: Fernando Nasser , insight@sources.redhat.com Subject: Re: Stack Window Problem [was: Re: DLLs and Insight...] Date: Thu, 01 Nov 2001 11:42:00 -0000 Message-id: <3BE1A584.C00E8BB9@cygnus.com> References: <3BD5A9E0.F58D0D66@redhat.com> <20011023140707.D23357@redhat.com> <3BE036A6.DBBBB5E2@redhat.com> <3BE04753.4AA1A1B9@redhat.com> <3BE054E0.9EAA172@redhat.com> X-SW-Source: 2001-q4/msg00247.html Ian Roxborough wrote: > > 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. > This ascertains that the GUI is innocent :) That said, lets see how we can track this down. > If it is stack corruption, would it be normal to vary between > similar versions of gdb? > I've never seen the bt output. Re-reading your message it seems that you got a sane stack trace -- just the symbolic information for the portions that are inside the Tk DLL are missing, right? (Maybe you should post the bt output) In the past, I had to manually load the DLL symbols in gdb. After making sure the DLL compiled with debugging symbols was the only one around and after stopping somewhere after it was loaded, I used the add-symbol command to load the DLL symbols in. After that was done, the backtrace had all symbolic info on it. You'll need the load address of the dll. The syntax is: add-symbol filename address -- Fernando Nasser Red Hat - Toronto E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9