From: Valentin Gatien-Baron <vgatien-baron@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29066-done@debbugs.gnu.org,
Andreas Schwab <schwab@linux-m68k.org>,
Mark Shinwell <mshinwell@janestreet.com>
Subject: bug#29066: 26.0.90; crash in gc involving buffer local symbols
Date: Tue, 31 Oct 2017 16:13:10 -0400 [thread overview]
Message-ID: <CAFd54qNT2pG2jO-jKnhML58fJ6QBG=r0UHtLXwjjGdd+z8NSPA@mail.gmail.com> (raw)
In-Reply-To: <83zi87rse9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Tue, Oct 31, 2017 at 4:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Valentin Gatien-Baron <vgatien-baron@janestreet.com>
> > Date: Tue, 31 Oct 2017 15:58:45 -0400
> > Cc: Andreas Schwab <schwab@linux-m68k.org>,
> > 29066@debbugs.gnu.org,
> > Mark Shinwell <mshinwell@janestreet.com>
> >
> > The slight downside of your fix is that there are dangling pointers
> that point to valid-looking things in the
> > debugger.
>
> How is that different from any other symbol on symbol_free_list?
>
Ok, maybe it's no different.
>
> > But I am not going to insist. There's nothing else to do, you can close
> the bug. Thanks!
>
> Thanks, done.
>
[-- Attachment #2: Type: text/html, Size: 1590 bytes --]
next prev parent reply other threads:[~2017-10-31 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 14:36 bug#29066: 26.0.90; crash in gc involving buffer local symbols Valentin Gatien-Baron
2017-10-30 20:38 ` Eli Zaretskii
2017-10-30 22:04 ` Valentin Gatien-Baron
2017-10-31 3:39 ` Eli Zaretskii
2017-10-31 6:32 ` Andreas Schwab
2017-10-31 14:52 ` Valentin Gatien-Baron
2017-10-31 19:10 ` Eli Zaretskii
2017-10-31 19:58 ` Valentin Gatien-Baron
2017-10-31 20:09 ` Eli Zaretskii
2017-10-31 20:13 ` Valentin Gatien-Baron [this message]
2017-10-31 18:59 ` Eli Zaretskii
2017-10-31 20:23 ` Andreas Schwab
2017-10-31 20:34 ` Eli Zaretskii
2017-10-31 21:03 ` Andreas Schwab
2017-10-31 21:08 ` Eli Zaretskii
2017-10-31 22:00 ` Andreas Schwab
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='CAFd54qNT2pG2jO-jKnhML58fJ6QBG=r0UHtLXwjjGdd+z8NSPA@mail.gmail.com' \
--to=vgatien-baron@janestreet.com \
--cc=29066-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mshinwell@janestreet.com \
--cc=schwab@linux-m68k.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.
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).