From: "Daniel Colascione" <dancol@dancol.org>
To: "Alan Mackenzie" <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
Daniel Colascione <dancol@dancol.org>,
emacs-devel@gnu.org
Subject: Re: Help please! To track down GC trying to free an already freed object.
Date: Tue, 2 Apr 2019 14:03:52 -0700 [thread overview]
Message-ID: <5adec1c4c1287f6a7b7eb63b832cc2cb.squirrel@dancol.org> (raw)
In-Reply-To: <20190402204653.GC25792@ACM>
> Hello, Eli.
>
> On Tue, Apr 02, 2019 at 22:21:26 +0300, Eli Zaretskii wrote:
>> > Date: Tue, 2 Apr 2019 12:09:59 -0700
>> > From: "Daniel Colascione" <dancol@dancol.org>
>> > Cc: emacs-devel@gnu.org
>> >
>> > rr is incredibly helpful for debugging this sort of problem. See
>> > https://rr-project.org/. You can record an rr session containing the
>> > crash, replay it, get to the crash, and then reverse-next,
>> reverse-finish,
>> > and reverse-continue your way through the GC, running it in reverse
>> until
>> > you find whatever it is that made mark_object on the dead object
>> happen.
>
>> GDB supports reverse execution as well, on some platforms.
>
> On my GNU/Linux system, I tried to run 'reverse-next', and got the error
> message:
>
> Target multi-thread does not support this command.
>
> . :-( I suppose I could reconfigure without multi threading, but then
> the bug (which is reproducible) probably wouldn't happen in the same
> place.
I don't think I've ever gotten pure-GDB reverse execution to work
correctly. rr Just Works for me in every instance I've tried it.
next prev parent reply other threads:[~2019-04-02 21:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 11:25 Help please! To track down GC trying to free an already freed object Alan Mackenzie
2019-04-02 15:04 ` Eli Zaretskii
2019-04-02 20:42 ` Alan Mackenzie
2019-04-03 4:43 ` Eli Zaretskii
2019-04-04 18:57 ` Alan Mackenzie
2019-04-02 19:09 ` Daniel Colascione
2019-04-02 19:21 ` Eli Zaretskii
2019-04-02 20:46 ` Alan Mackenzie
2019-04-02 21:03 ` Daniel Colascione [this message]
2019-04-03 4:39 ` Eli Zaretskii
2019-04-03 10:01 ` Alan Mackenzie
2019-04-03 10:12 ` Eli Zaretskii
2019-04-03 15:23 ` Paul Eggert
2019-04-02 20:24 ` Alan Mackenzie
2019-04-02 20:33 ` Daniel Colascione
2019-04-02 21:00 ` Alan Mackenzie
2019-04-05 4:49 ` Alex
2019-04-05 8:26 ` Alan Mackenzie
2019-04-05 17:05 ` Comparing symbol-with-position using eq (was: Help please! To track down GC trying to free an already freed object.) Alex
2019-04-05 18:21 ` Comparing symbol-with-position using eq Alan Mackenzie
2019-04-05 20:18 ` Daniel Colascione
2019-04-05 21:54 ` Alan Mackenzie
2019-04-05 22:50 ` Paul Eggert
2019-04-06 12:23 ` Clément Pit-Claudel
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=5adec1c4c1287f6a7b7eb63b832cc2cb.squirrel@dancol.org \
--to=dancol@dancol.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).