Re: another crash -- this time at startup

[Alex Schroeder]

"Eli Zaretskii" <address@hidden> writes:

>> From: Alex Schroeder <address@hidden>
>> Date: Sat, 25 Jan 2003 01:28:51 +0100
>> 
>> Program received signal SIGSTOP, Stopped (signal).
>> 0x4032dc14 in malloc () from /lib/libc.so.6
>> (gdb) bt
>> #0  0x4032dc14 in malloc () from /lib/libc.so.6
>
> Crashes in malloc usually mean some code smashed allocated buffers
> somewhere else.  However, I'm confused by SIGSTOP: it's not a normal
> crash, AFAIK.
>
> Can anyone think of a reason for crashing with SIGSTOP?

I am confused myself.  I just got it today again.  The only thing I
remember doing differently is that I did not immediately hit RET and c
to continue; I waited a few seconds.  Then I hit c.  And then I get
the SIGSTOP.  And just out of curiosity I hit c again.  And no problem
-- Emacs continued.  So perhaps this is some weird interaction between
GDB, Emacs, or the window manager (ratpoison).  Who knows.

For the moment it seems that this is not critical.

Alex.

...
Loaded symbols for /usr/X11R6/lib/X11/locale/common/ximcp.so.2
Reading symbols from /usr/X11R6/lib/X11/locale/common/xomGeneric.so.2...done.
Loaded symbols for /usr/X11R6/lib/X11/locale/common/xomGeneric.so.2
0x40381bbe in __xstat64 () from /lib/libc.so.6
DISPLAY = :0.0
TERM = xterm
Breakpoint 1 at 0x80d1e0e: file emacs.c, line 389.
Breakpoint 2 at 0x80b73fe: file xterm.c, line 11997.
(gdb) c
Continuing.

Program received signal SIGSTOP, Stopped (signal).
0x40381bbe in __xstat64 () from /lib/libc.so.6
(gdb) c
Continuing.