From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>,
Dmitry Antipov <dmantipov@yandex.ru>
Cc: 17771@debbugs.gnu.org
Subject: bug#17771: 24.3.91; SIGSEGV in cleanup_vector
Date: Fri, 13 Jun 2014 17:52:22 +0300 [thread overview]
Message-ID: <83fvj8x3o9.fsf@gnu.org> (raw)
In-Reply-To: <87d2ec7v8p.fsf@rosalinde.fritz.box>
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 17771@debbugs.gnu.org
> Date: Fri, 13 Jun 2014 16:13:42 +0200
>
> > I installed a trivial workaround for that in r117235 on the emacs-24
> > branch. The diffs are below. Can you try this and see if the problem
> > is solved? It's possible that the real problem is somewhere else, in
> > which case you will probably see it when you apply the patch.
>
> With the patch, Emacs still crashes with the same recipe, but the first
> frame of backtrace is different (looks like not in Emacs):
I think it's just a bogus pointer to the font driver, and somehow
valid_font_driver doesn't catch it in time.
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000c260b2 in ?? ()
> (gdb) bt full
> #0 0x0000000000c260b2 in ?? ()
> No symbol table info available.
> #1 0x00000000005aa580 in cleanup_vector (vector=0x3dd52c8)
> at ../../../../bzr/emacs/emacs-24/src/alloc.c:2935
> drv = 0x3dd5130
> #2 0x00000000005aa686 in sweep_vectors ()
> at ../../../../bzr/emacs/emacs-24/src/alloc.c:2974
> total_bytes = 140737488344592
> free_this_block = false
> nbytes = 1048
> block = 0x3dd4680
> bprev = 0xbf1060
> lv = 0x6282a3 <balance_intervals+31>
> lvprev = 0xbf2070
> vector = 0x3dd52c8
> next = 0x3dd52c8
> #3 0x00000000005b0141 in gc_sweep () at ../../../../bzr/emacs/emacs-24/src/alloc.c:6721
So Dmitry, I think Stephen here just found you a perfect recipe to
reproduce bug #16140, something that I failed to do. Could you please
look into this?
Thanks.
next prev parent reply other threads:[~2014-06-13 14:52 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
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 [this message]
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=83fvj8x3o9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17771@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--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).