From: Tom Tromey <tromey@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB crashing because of Python
Date: Tue, 28 Aug 2012 19:45:00 -0000 [thread overview]
Message-ID: <87zk5eer7s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87wr0kgumi.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 27 Aug 2012 10:36:05 -0600")
Kevin> so based on `git bisect`, it looks like the errors were introduced by
Kevin> this commit:
Tom> Can you please try the appended patch?
I spent some time today trying to make a robust test case for this.
I can see the error clearly with valgrind, but I can't make it crash.
Printing the Objfile reference counts "works" but it seems to not be
very robust -- in the failing case the count appears to be 12 on my
machine, but of course this is just a fluke, and it could well be
anything.
-lmcheck unfortunately doesn't help, because Python is typically built
using its own allocator. It would be nice if we could disable this for
the test suite -- it is automatically disabled under valgrind (under
some typical configurations), so it could be done cheaply -- but this
isn't available.
Anyway, I'm going to write a ChangeLog and send it to the patch list.
Tom
next prev parent reply other threads:[~2012-08-28 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 13:21 Kevin Pouget
2012-08-23 13:56 ` Tom Tromey
2012-08-23 14:30 ` Kevin Pouget
2012-08-23 18:52 ` Tom Tromey
2012-08-27 16:05 ` Kevin Pouget
2012-08-27 16:36 ` Tom Tromey
2012-08-27 16:39 ` Tom Tromey
2012-08-28 19:45 ` Tom Tromey [this message]
2012-08-29 8:14 ` Kevin Pouget
2012-09-06 19:27 ` Tom Tromey
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=87zk5eer7s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.com \
/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.
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).