"Bert 'theBlackDragon' Geens" <[EMAIL PROTECTED]> writes:
> On 6/12/05, Dan Espen <[EMAIL PROTECTED]> wrote:
> > "Bert 'theBlackDragon' Geens" <[EMAIL PROTECTED]> writes:
> > > I'm experiencing some weird crashes when swallowing an FvwmScript in an=
> =3D20
> > > FvwmButtons (which is then used in a Panel), most notably this started=
> =3D20
> > > happening after having added a progress bar, everything worked fine bef=
> ore=3D
> > > =3D20
> > > that, it also works fine when it's not being swallowed.
> >=20
> > What release of fvwm are you using?
>
> That would be 2.5.12 from Gentoo portage.
>
> > > All relevant files can be found here: http://www.lair.be/files/error/
> > The stack trace doesn't seem to show anything.
> > It looks like fvwm was built without debug symbols.
> > If you could build it with debug symbols (the default)
> > that would help.
>
> Well I recompiled Fvwm with the 'debug' use flag, this got me a lot of
> debug output and the crashes have become less regular, this time I got
> this:
>
> 10:32:28 0 [FVWM][My_XNextEvent]: <<DEBUG>> leaving My_XNextEvent
Fvwm debug wasn't what I was looking for.
I find this is the stack trace:
This GDB was configured as "i386-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
warning: core file may not match specified executable file.
(no debugging symbols found)
Core was generated by `/usr/lib/fvwm/2.5.12/FvwmScript 37 4 none 0 8
/home/theBlackDragon/.fvwm/script'.
Program terminated with signal 6, Aborted.
#0 0xb7cb3bc1 in ?? ()
(gdb) where
#0 0xb7cb3bc1 in ?? ()
#1 0xb7cb3795 in ?? ()
^^^^^^^^^^ ^^
I'd like to see line numbers and function names instead of offsets.
Usually we get function names by compiling with '-g' which should
be the default.
Perhaps you're not invoking gdb correctly? Make sure
you point to the correct FvwmScript.
--
Dan Espen E-mail: [EMAIL PROTECTED]
