GnuCash 1.8.1 Crash

[Craig Lanning]

On Thu, 2003-02-13 at 08:38, Derek Atkins wrote:
> Hmm.  Well, do you feel confident about running gnucash under gdb?
> You would need to:
> 
>         gnucash-env gdb /usr/bin/guile
>         ...
>         gdb> run -e main -s /usr/libexec/overrides/gnucash

I think you meant

gdb> run -e main -s /usr/libexec/gnucash/overrides/gnucash

Below is the output from the gdb session.  If it would be useful I could
try to recompile guile and run it not stripped later today.

Craig

> And then, perhaps, set a breakpoint in either exit() or _exit()
> and let it run to completion.  Then get a gdb "backtrace"...
> 
> Thanks,
> 
> -derek

[craig at parentz craig]$ gnucash-env gdb /usr/bin/guile
GNU gdb Red Hat Linux (5.3post-0.20021129.11rh)
Copyright 2002 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-gnu"...
(no debugging symbols found)...
(gdb) run -e main -s /usr/libexec/gnucash/overrides/gnucash
Starting program: /usr/bin/guile -e main -s /usr/libexec/gnucash/overrides/gnucash
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 1075024544 (LWP 3364)]

Program received signal SIGINT, Interrupt.
[Switching to Thread 1075024544 (LWP 3364)]
0xffffe002 in ?? ()
(gdb) break exit()
Function "exit()" not defined.
(gdb) break _exit()
Function "_exit()" not defined.
(gdb) cont
Continuing.
ERROR: missing or extra expression

Program exited with code 02.
(gdb) backtrace
No stack.
(gdb) quit
[craig at parentz craig]$