From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Tom Tromey <tromey@redhat.com>
Subject: Re: Re-evaluate floating varobj as part of varobj_invalidate.
Date: Thu, 26 Jul 2012 08:35:00 -0000 [thread overview]
Message-ID: <20120726083511.GA16614@host2.jankratochvil.net> (raw)
In-Reply-To: <87vchbhgo9.fsf@fleche.redhat.com>
On Wed, 25 Jul 2012 19:52:22 +0200, Tom Tromey wrote:
> >>>>> "Andrew" == Andrew Burgess <aburgess@broadcom.com> writes:
>
> Andrew> I have a bug & patch, but no great way to reproduce the issue as
> Andrew> it's a use of pointer after free issue,
>
> I suspect the recent-ish change to use -lmcheck by default will cause us
> to catch this bug in the test suite, at least on glibc-using systems.
Yes, FSF GDB HEAD crashes for me with the posted reproducer. Could you write
this simple testcase?
Thanks,
Jan
next prev parent reply other threads:[~2012-07-26 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 16:59 Andrew Burgess
2012-07-25 17:52 ` Tom Tromey
2012-07-26 8:35 ` Jan Kratochvil [this message]
2012-07-27 8:21 ` Andrew Burgess
2012-07-27 14:06 ` Jan Kratochvil
2012-07-30 12:27 ` Andrew Burgess
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=20120726083511.GA16614@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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