On Sun, 20 Feb 2005, Justin Pryzby wrote:
Could you try running MALLOC_CHECK_=1 gaim? See if that reports
anything. Or, if MALLOC_CHECK_ is already set, unset it (indeed, that
itself could cause the abort).
LD_LIBRARY_PATH=/usr/lib/debug MALLOC_CHECK_=1 gdb gaim
[...]
Program received
On Sun, Feb 20, 2005 at 08:44:51PM +0200, Martin-Éric Racine wrote:
On Sun, 20 Feb 2005, Justin Pryzby wrote:
Could you try running MALLOC_CHECK_=1 gaim? See if that reports
anything. Or, if MALLOC_CHECK_ is already set, unset it (indeed, that
itself could cause the abort).
On Sun, 20 Feb 2005, Justin Pryzby wrote:
On Sun, Feb 20, 2005 at 08:44:51PM +0200, Martin-Éric Racine wrote:
On Sun, 20 Feb 2005, Justin Pryzby wrote:
Could you try running MALLOC_CHECK_=1 gaim? See if that reports
anything. Or, if MALLOC_CHECK_ is already set, unset it (indeed,
(gdb) run --g-fatal-warnings
Starting program: /usr/bin/gaim --g-fatal-warnings
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 18458)]
malloc: using debugging hooks
Program received signal SIGABRT, Aborted.
[Switching to Thread 16384 (LWP 18458)]
4 matches
Mail list logo
