From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Emacs coredump when reading news.gmane.org gwene.com.stackoverflow.blog:138
Date: Mon, 11 Jul 2011 12:11:51 +0200 [thread overview]
Message-ID: <87y605p1nc.fsf@topper.koldfront.dk> (raw)
When I display this article from news.gwene.org:
Xref: news.gmane.org gwene.com.stackoverflow.blog:138
Message-ID: <x1-W1MlTfbFlIoISoajauUqJC8kpAc@gwene.org>
in:
GNU Emacs 24.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.4) of
2011-07-05 on cigue, modified by Debian (emacs-snapshot 1:20110705-1
by Julien Danjou)
No Gnus v0.18 (fbfc2ce2, from git)
the article is shown, but after a couple of seconds, I get a coredump.
Running "gdb emacs core" and typing "bt", I get:
$ gdb emacs core
GNU gdb (GDB) 7.2-debian
[...]
Reading symbols from /usr/bin/emacs...(no debugging symbols found)...done.
[New Thread 6327]
[New Thread 6328]
[New Thread 6329]
[...]
Core was generated by `emacs'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f82feb686e7 in kill () at ../sysdeps/unix/syscall-template.S:82
82 ../sysdeps/unix/syscall-template.S: No such file or directory.
in ../sysdeps/unix/syscall-template.S
(gdb) bt
#0 0x00007f82feb686e7 in kill () at ../sysdeps/unix/syscall-template.S:82
#1 0x00000000004ff4ca in ?? ()
#2 <signal handler called>
#3 0x00000000004e8e56 in ?? ()
#4 0x00000000004e75c8 in ?? ()
#5 0x00000000004e7916 in ?? ()
#6 0x000000000057585c in ?? ()
#7 0x00000000005ada46 in ?? ()
#8 0x0000000000575319 in ?? ()
#9 0x000000000057568b in ?? ()
#10 0x00000000005ada46 in ?? ()
#11 0x0000000000575319 in ?? ()
#12 0x000000000057568b in ?? ()
#13 0x00000000005766b7 in ?? ()
#14 0x00000000005758cf in ?? ()
#15 0x00000000005ada46 in ?? ()
#16 0x0000000000574c8b in ?? ()
#17 0x0000000000577f14 in ?? ()
#18 0x00000000005ae389 in ?? ()
#19 0x0000000000575319 in ?? ()
#20 0x000000000057568b in ?? ()
#21 0x0000000000575b0a in ?? ()
#22 0x000000000050591e in ?? ()
#23 0x0000000000505c49 in ?? ()
#24 0x0000000000507f65 in ?? ()
#25 0x000000000050a68a in ?? ()
#26 0x00000000005b3ede in ?? ()
#27 0x0000000000421954 in ?? ()
#28 0x000000000050c999 in ?? ()
#29 0x000000000050d6fd in ?? ()
#30 0x000000000050f3b7 in ?? ()
#31 0x0000000000573983 in ?? ()
#32 0x000000000050259e in ?? ()
#33 0x0000000000573858 in ?? ()
#34 0x0000000000503aff in ?? ()
#35 0x0000000000503e37 in ?? ()
#36 0x0000000000416d4d in ?? ()
#37 0x00007f82feb54ead in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>,
init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff4f5093d8) at libc-start.c:228
#38 0x0000000000417945 in ?? ()
#39 0x00007fff4f5093d8 in ?? ()
#40 0x000000000000001c in ?? ()
---Type <return> to continue, or q <return> to quit---
#41 0x0000000000000001 in ?? ()
#42 0x00007fff4f50b567 in ?? ()
#43 0x0000000000000000 in ?? ()
(gdb)
which, I'm afraid, doesn't say much...?
Can anyone reproduce this crash?
Best regards,
Adam
--
"Most people dismiss such thinking as 'impractical' Adam Sjøgren
and 'unrealistic.' I think most people are being asjo@koldfront.dk
unimaginative."
next reply other threads:[~2011-07-11 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 10:11 Adam Sjøgren [this message]
2011-07-12 6:08 ` Reiner Steib
2011-07-12 9:50 ` Adam Sjøgren
2011-07-12 10:50 ` Tassilo Horn
2011-07-12 21:43 ` Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y605p1nc.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).