Before the "run -sync", do "break exit". This should put in a breakpoint before
the program exits. There's some good general info on tracing these things down
in the BUG_REPORTING file from the lesstif distribution.
On 13-Jul-00 at 20:21, R. Lahaye ([EMAIL PROTECTED]) wrote:
> Rick Scott wrote:
> >
> > The "X connection to :0.0 broken (explicit kill or server shutdown)." is
> > normal if you "kill" an app instead of "close". Neither should segfault.
> > If we are getting a fault, a backtrace with -sync should narrow it down
> > rather quickly, if it is related to the recent changes....
>
> Hmm, can't get that info, but I remember being not so skillful
> in debugging. Here's what I've done:
>
> 1) configured lesstif with "--enable-debug"
> compiled it with "-g -O0" options
> installed it in /usr/local/lesstif
>
> 2) configured Grace with "--enable-debug"
> compiled it with "-g -O0" options
>
> When I run Grace with gdb and create the crash, I get:
>
> =================================================================
>
> $ gdb src/xmgrace
> GNU gdb 19991004
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "i386-redhat-linux"...
> (gdb) run -sync
> Starting program: /home/software/GRACE/grace/src/xmgrace -sync
> X connection to mapt11105:0.0 broken (explicit kill or server shutdown).
>
> Program exited with code 01.
> (gdb) where
> No stack.
> (gdb)
>
> =======================================================================
>
> Am I doing something wrong, or is this bug difficult to trace?
>
> Regards,
>
> Rob.
>
>
