Re: Crash in show_busy_cursor.

[Eli Zaretskii]

> From: Gerd Moellmann <address@hidden>
> Date: 01 Dec 2000 13:49:47 +0100
> 
> > (I can't even get this show_busy_cursor to be called when running
> > under the debugger), so I cannot get any more information (like
> > register values etc).
> 
> handle SIGALRM ignore
> 
> in .gdbinit?

Actually, in GDB you can simply deliver SIGALRM to the debuggee
whenever you like:

  (gdb) signal SIGALRM

To arrange this, put a breakpoint anywhere in the code whose execution
you can control by some external event, such as a mouse click on a
certain area, and when GDB stops Emacs, deliver the signal as shown
above.

> I think it would be useful to look at the value of `frame' when it
> happens the next time, or maybe even the car of `rest'.  With GDB's
> xframe, we'd get the real value of `f' that was used here.
> 
> In my limited experience with crashes on Sparcs, the SEGV almost
> always screws up the values of local variables beyond recognition.
> Many backtraces I get for example, list parameter values, which simply
> can't be true because Emacs would have crashed with them much
> earlier.

I think disassembly shows that the problem was with with the `core'
member of the widget dereferenced by the call to XCreateWindow.