[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: crash when opening a newsgroup
From: |
Timmy Douglas |
Subject: |
Re: crash when opening a newsgroup |
Date: |
Fri, 29 Apr 2005 01:25:13 -0400 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) |
Richard Stallman <address@hidden> writes:
> 'backtrace_list' appears to only contain two items, and it looks like
> the first one is semi-corrupted also.
>
> It does look that way. The innermost element of backtrace_list should
> have been made by the innermost Lisp-level function call. An ordinary
> backtrace should show us what that was.
I'm not sure if this helps any but I happened to be running emacs and
it crashed again (I don't think it was running in gdb but it seemed
like gdb latched onto it when it died??):
Side note: one thing that would be nice is if emacs would always crash
instead of aborting...sometimes I run it outside of gdb and
aborting is like exiting cleanly (I think?) so there is no way
to figure out what went wrong.
(emacs:7576): GLib-GObject-WARNING **: invalid unclassed pointer in cast to
`GtkMenuItem'
(emacs:7576): GLib-GObject-WARNING **: invalid unclassed pointer in cast to
`GtkBin'
(emacs:7576): Gtk-CRITICAL **: gtk_bin_get_child: assertion `GTK_IS_BIN (bin)'
failed
(emacs:7576): Gtk-CRITICAL **: gtk_label_get_label: assertion `GTK_IS_LABEL
(label)' failed
Cannot access memory at address 0xbfffd570
(gdb) bt
#0 0xb772dbb1 in kill () at string2.h:1000
#1 0x0811eb0b in fatal_error_signal (sig=-1073755232) at emacs.c:423
#2 0xb7a4af37 in __pthread_sighandler (signo=Cannot access memory at address
0xbfffcc28
) at sighandler.c:39
#3 <signal handler called>
#4 0x08185c1c in Fsignal (error_symbol=Cannot access memory at address
0xbfffcd20
) at eval.c:1543
#5 0x08185f21 in error (m=Cannot access memory at address 0xbfffd008
) at eval.c:1812
#6 0x081ba00f in send_process (proc=Cannot access memory at address 0xbfffd138
) at process.c:5411
#7 0x08185297 in funcall_lambda (fun=Cannot access memory at address 0xbfffd190
) at eval.c:2974
#8 0x081856a5 in Ffuncall (nargs=Cannot access memory at address 0xbfffd1d8
) at eval.c:2843
#9 0x08186b8f in Fapply (nargs=Cannot access memory at address 0xbfffd248
) at eval.c:2284
#10 0x08185932 in Ffuncall (nargs=Cannot access memory at address 0xbfffd2c8
) at eval.c:2767
#11 0x081b0df5 in Fbyte_code (bytestr=Cannot access memory at address 0xbfffd32c
) at bytecode.c:686
#12 0x08185297 in funcall_lambda (fun=Cannot access memory at address 0xbfffd3d0
) at eval.c:2974
#13 0x081856a5 in Ffuncall (nargs=Cannot access memory at address 0xbfffd418
) at eval.c:2843
#14 0x081b0df5 in Fbyte_code (bytestr=Cannot access memory at address 0xbfffd47c
) at bytecode.c:686
#15 0x08185297 in funcall_lambda (fun=Cannot access memory at address 0xbfffd510
) at eval.c:2974
Cannot access memory at address 0xbfffd518
(gdb) frame 4
#4 0x08185c1c in Fsignal (error_symbol=Cannot access memory at address
0xbfffcd20
) at eval.c:1543
1543 if (bp && bp->function && EQ (*bp->function, Qerror))
(gdb) p *bp
Cannot access memory at address 0xbfffcd2c
(gdb) p *backtrace_list
Cannot access memory at address 0xbfffd570
I have no idea what's going on here...
- crash when opening a newsgroup, Timmy Douglas, 2005/04/24
- Re: crash when opening a newsgroup, Richard Stallman, 2005/04/24
- Re: crash when opening a newsgroup, Timmy Douglas, 2005/04/24
- Re: crash when opening a newsgroup, Eli Zaretskii, 2005/04/25
- Re: crash when opening a newsgroup, Richard Stallman, 2005/04/26
- Re: crash when opening a newsgroup, Timmy Douglas, 2005/04/26
- Re: crash when opening a newsgroup, Richard Stallman, 2005/04/27
- Re: crash when opening a newsgroup, Timmy Douglas, 2005/04/28
- Re: crash when opening a newsgroup, Richard Stallman, 2005/04/28
- Re: crash when opening a newsgroup,
Timmy Douglas <=