On Mon, Jul 02, 2001 at 09:23:38AM +0930, Berndt Josef Wulf wrote:
> 
> Sofar, I've been unable to track this problem down. gdb will dump core
> on attempts to read the artsd core file. A trace of gdb's core dump
> will reveal the following:
> 
> (gdb) where
> #0  0x481461a6 in cplus_demangle ()
> #1  0x48146110 in cplus_demangle ()
> #2  0x4814657a in cplus_demangle ()
> #3  0x48142fbd in cplus_demangle ()
> #4  0x48142902 in cplus_demangle ()
> #5  0x48142836 in cplus_demangle ()
> #6  0x808b7a4 in dladdr ()
> #7  0x80925a1 in dladdr ()
> #8  0x80675fa in dladdr ()
> #9  0x8067794 in dladdr ()
> #10 0x806799d in dladdr ()
> #11 0x804bc67 in dladdr ()
> #12 0x804afc5 in free ()
> 
> Should I PR this? 

Definitely.  If the debugger core dumps looking at a core dump that is
a serious issue.  Perhaps this problem is already solved with the new
toolchain that is being worked on.

-Andrew