From: sami wagiaalla <swagiaal@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] PR 12028 "GDB crashes on a double free during overload resolution"
Date: Thu, 23 Sep 2010 18:46:00 -0000 [thread overview]
Message-ID: <4C9B7CB1.7030208@redhat.com> (raw)
In-Reply-To: <m3pqw57fi0.fsf@fleche.redhat.com>
On 09/22/2010 03:19 PM, Tom Tromey wrote:
>>>>>> "Sami" == sami wagiaalla<swagiaal@redhat.com> writes:
>
> Sami> I agree. I have attached a patch which has been regression tested on
> Sami> x8664 with gcc-4.4.4-10.fc13
>
> This patch is also ok, assuming that it is still valgrind-clean for the
> test in question.
>
I ran valgrind like this:
valgrind ./gdb/gdb ./gdb/testsuite/gdb.cp/pr12028 -ex 'sta' -ex 'p
D::foo(b)' -ex 'q'
There are no glaring errors. The original double free error is still
gone of course and there are no others.
Incidentally, there is this error:
==8467== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 27 from 9)
==8467== Use of uninitialised value of size 8
==8467== at 0x57C966: bcache_full (bcache.c:189)
==8467== by 0x52E94F: add_psymbol_to_list (psymtab.c:1358)
==8467== by 0x596634: add_partial_symbol (dwarf2read.c:3794)
==8467== by 0x596A7A: add_partial_subprogram (dwarf2read.c:3882)
Worth figuring out but it is unrelated to this patch series. So I am
committing the above patch.
next prev parent reply other threads:[~2010-09-23 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 9:25 sami wagiaalla
2010-09-19 17:39 ` Doug Evans
2010-09-22 18:12 ` sami wagiaalla
2010-09-22 19:36 ` Tom Tromey
2010-09-23 18:46 ` sami wagiaalla [this message]
2010-09-27 18:02 ` Tom Tromey
2010-09-28 16:32 ` sami wagiaalla
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=4C9B7CB1.7030208@redhat.com \
--to=swagiaal@redhat.com \
--cc=dje@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).