From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 17771@debbugs.gnu.org
Subject: bug#17771: 24.3.91; SIGSEGV in cleanup_vector
Date: Fri, 13 Jun 2014 15:19:50 +0300 [thread overview]
Message-ID: <83tx7pvw61.fsf@gnu.org> (raw)
In-Reply-To: <87zjhh6su4.fsf@rosalinde.fritz.box>
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 17771@debbugs.gnu.org
> Date: Fri, 13 Jun 2014 11:50:59 +0200
>
> On Fri, 13 Jun 2014 12:41:56 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> From: Stephen Berman <stephen.berman@gmx.net>
> >> Date: Fri, 13 Jun 2014 11:12:44 +0200
> >>
> >>
> >> 0. emacs -Q
> >> 1. C-h h (on my machine, it takes ~30 seconds for the Hello file to
> >> appear; during that time, do the following:)
> >> 2. Type C-g repeatedly (I did it rapidly, for ~15 seconds).
> >> 3. Emacs crashes, full backtrace below. (This is reliably reproducible.)
> >
> > Not here, but this is Windows, where input is treated very
> > differently.
> >
> >> Program received signal SIGSEGV, Segmentation fault.
> >> 0x00000000005aa564 in cleanup_vector (vector=0x43b4ea8)
> >> at ../../../../bzr/emacs/emacs-24/src/alloc.c:2929
> >> 2929 ((struct font *) vector)->driver->close ((struct font *) vector);
> >
> > So which one is the bad pointer, vector, vector->driver, or
> > vector->driver->close?
>
> If you're asking me, can you tell me what to type in gdb to find out?
(gdb) p vector
(gdb) p vector->driver
(gdb) p vector->driver->close
Thanks.
next prev parent reply other threads:[~2014-06-13 12:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:12 bug#17771: 24.3.91; SIGSEGV in cleanup_vector Stephen Berman
2014-06-13 9:41 ` Eli Zaretskii
2014-06-13 9:50 ` Stephen Berman
2014-06-13 12:19 ` Eli Zaretskii [this message]
2014-06-13 12:39 ` Stephen Berman
2014-06-13 13:28 ` Eli Zaretskii
2014-06-13 13:34 ` Stephen Berman
2014-06-13 13:44 ` Eli Zaretskii
2014-06-13 13:53 ` Stephen Berman
2014-06-13 13:58 ` Eli Zaretskii
2014-06-13 14:13 ` Stephen Berman
2014-06-13 14:52 ` Eli Zaretskii
2014-06-16 8:02 ` Dmitry Antipov
2014-06-16 10:16 ` Stephen Berman
2014-06-16 12:37 ` Dmitry Antipov
2014-06-16 13:07 ` Stephen Berman
2014-06-16 13:19 ` Dmitry Antipov
2014-06-16 13:32 ` Andreas Schwab
2014-06-16 15:49 ` Stephen Berman
2014-06-16 16:21 ` Dmitry Antipov
2014-06-16 21:34 ` Stephen Berman
2014-06-17 2:25 ` Dmitry Antipov
2014-06-17 13:40 ` Stephen Berman
2014-06-18 12:54 ` Wolfgang Jenkner
2014-06-18 13:50 ` Stephen Berman
2014-06-18 14:01 ` Dmitry Antipov
2014-06-18 16:00 ` Stephen Berman
2014-06-18 16:24 ` Dmitry Antipov
2014-06-18 17:00 ` Stephen Berman
2014-08-12 3:59 ` Glenn Morris
2014-06-16 15:49 ` Stephen Berman
2014-06-16 16:03 ` Dmitry Antipov
2014-06-16 21:33 ` Stephen Berman
2014-06-17 2:09 ` Dmitry Antipov
2014-06-17 13:41 ` Stephen Berman
2014-06-17 18:11 ` Dmitry Antipov
2014-06-18 13:50 ` Stephen Berman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tx7pvw61.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17771@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).