From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 9006@debbugs.gnu.org
Subject: bug#9006: 24.0.50; Abort in unshow_buffer/kill-buffer
Date: Wed, 13 Jul 2011 03:24:53 -0400 [thread overview]
Message-ID: <E1QgtoT-0005Jx-Ca@fencepost.gnu.org> (raw)
In-Reply-To: <87hb6qd63k.fsf@escher.fritz.box> (message from Stephen Berman on Wed, 13 Jul 2011 08:53:19 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Wed, 13 Jul 2011 08:53:19 +0200
> Cc: 9006@debbugs.gnu.org
>
> I was in the process of replying that I was well past the twelfth hour
> and Emacs was still going strong -- when Emacs crashed :-(.
> But: I think this crash is not related to your patch to
> vertical_motion -- it happened in compute_line_metrics -- so I still
> think you should install it.
The crash happens during redisplay of mode line.
> PS: On the chance that this crash could be relevant, here are the
> circumstances and the backtrace. I was in Gnus, had just opened your
> post again to reply, and somehow I mistakenly must have type `C-s SPC',
> because all the spaces in the Summary buffer became covered with
> lazy-highlight face. I typed C-g two or three times -- and Emacs
> crashed hard (segfault); bt full gave no Lisp backtrace. I have not
> been able to reproduce this.
>
> #0 0x080735ac in compute_line_metrics (it=0xbfffb004)
> at /data/steve/bzr/emacs/quickfixes/src/xdisp.c:16789
Please tell what source line corresponds to the PC address 0x080735ac
in your version of the sources. It's not clear what code caused the
segfault, and in an optimized build one cannot trust line numbers
reported by the debugger in a backtrace. You may need to disassemble
the code in GDB to see what source line crashed.
Also, please go to frame #1 (assuming that crashed session still
exists), and type "p *it.glyph_row", then post here what GDB prints.
next prev parent reply other threads:[~2011-07-13 7:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 23:20 bug#9006: 24.0.50; Abort in unshow_buffer/kill-buffer Stephen Berman
2011-07-06 9:25 ` martin rudalics
2011-07-06 19:19 ` Stephen Berman
2011-07-07 8:23 ` martin rudalics
2011-07-07 9:32 ` Stephen Berman
2011-07-07 15:47 ` martin rudalics
2011-07-08 23:03 ` Stephen Berman
2011-07-09 8:44 ` martin rudalics
2011-07-09 11:57 ` Stephen Berman
2011-07-09 13:01 ` martin rudalics
2011-07-09 16:27 ` Stephen Berman
2011-07-09 16:54 ` Stephen Berman
2011-07-10 8:59 ` martin rudalics
2011-07-10 10:25 ` Stephen Berman
2011-07-10 13:30 ` martin rudalics
2011-07-10 20:31 ` Stephen Berman
2011-07-11 19:14 ` martin rudalics
2011-07-11 20:04 ` Stephen Berman
2011-07-12 8:36 ` martin rudalics
2011-07-12 8:51 ` Stephen Berman
2011-07-13 6:53 ` Stephen Berman
2011-07-13 7:24 ` Eli Zaretskii [this message]
2011-07-13 8:00 ` Stephen Berman
2011-07-13 10:03 ` Eli Zaretskii
2011-07-13 11:40 ` Stephen Berman
2011-07-13 8:37 ` martin rudalics
2011-07-13 10:05 ` Eli Zaretskii
2011-07-13 11:54 ` martin rudalics
2011-07-13 12:20 ` Stephen Berman
2011-07-13 11:39 ` Stephen Berman
2011-07-14 8:35 ` martin rudalics
2011-07-15 21:05 ` Stephen Berman
2011-07-10 8:58 ` martin rudalics
2011-07-09 12:44 ` Stephen Berman
2011-07-09 13:01 ` martin rudalics
2011-07-09 17:31 ` Eli Zaretskii
2011-07-10 8:59 ` martin rudalics
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=E1QgtoT-0005Jx-Ca@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9006@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.