From: Brad Roberts <braddr@puremagic.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: patch for crash in d-lang.c's demangler
Date: Tue, 10 Aug 2010 23:15:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1008101614150.23754@slice-2.puremagic.com> (raw)
In-Reply-To: <m3k4ny9kql.fsf@fleche.redhat.com>
On Tue, 10 Aug 2010, Tom Tromey wrote:
> >>>>> "Brad" == Brad Roberts <braddr@puremagic.com> writes:
>
> I think your patch is reasonable, but the line just after your change is
> weird:
>
> > if (i <= 0 && strlen (mangled_str) < i)
> > return 0;
>
> I don't think that condition can ever be true.
Agreed. Your patch looks good. I feel guilty about not contributing a
unit test to cover this case, so I shouldn't poke you about not adding one
either, but if you feel like feeling that guilty... :)
Thanks,
Brad
next prev parent reply other threads:[~2010-08-10 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 21:10 Brad Roberts
2010-08-10 22:17 ` Tom Tromey
2010-08-10 23:15 ` Brad Roberts [this message]
2010-08-11 1:52 ` Tom Tromey
2010-08-11 15:41 ` 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=alpine.DEB.2.00.1008101614150.23754@slice-2.puremagic.com \
--to=braddr@puremagic.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