From: Sami Wagiaalla <swagiaal@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: GDB crash due to endless recursion in namespace lookup
Date: Fri, 25 Jun 2010 16:56:00 -0000 [thread overview]
Message-ID: <4C24DB95.5000806@redhat.com> (raw)
In-Reply-To: <201006251624.o5PGOHAX014293@d12av02.megacenter.de.ibm.com>
> Oops, I didn't see your email and just checked in a fix myself (which
> seems more or less the same as yours) ... Sorry for the confusion!
>
Cool. Thanks :) I had the fix ready yesterday but the testsuite takes a
while to run on my machine, but I should have replied to your email :).
>> 2010-06-24 Sami Wagiaalla<swagiaal@redhat.com>
>>
>> * gdb.cp/operator.cc: Created an import loop.
>> * gdb.cp/operator.exp: Added testcase for import loop.
>
> Except I didn't add the test case since on my machine, I already had
> several other tests failing due to the bug. But I guess you're right,
> we should add the test anyway, for machines without the loop in the
> system headers ... Please feel free to check in the test!
>
will do.
> Thanks for the quick fix!
No problem
Sami
next prev parent reply other threads:[~2010-06-25 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 18:10 Ulrich Weigand
2010-06-25 15:46 ` sami wagiaalla
2010-06-25 16:24 ` Ulrich Weigand
2010-06-25 16:56 ` Sami Wagiaalla [this message]
2010-06-25 16:20 ` [commit] Fix " Ulrich Weigand
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=4C24DB95.5000806@redhat.com \
--to=swagiaal@redhat.com \
--cc=gdb-patches@sourceware.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.
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).