From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR symtab/11464
Date: Mon, 11 Feb 2013 20:39:00 -0000 [thread overview]
Message-ID: <20130211203930.GA26149@host2.jankratochvil.net> (raw)
In-Reply-To: <87zjzappd6.fsf@fleche.redhat.com>
On Mon, 11 Feb 2013 21:28:05 +0100, Tom Tromey wrote:
> This is quite strange. Today I rebased this patch onto gdb/master.
> Then I built gdb without the patch and ran the test case that was
> included in the patch. In gdb.log I then see:
>
> ptype gnu_obj_1::'~gnu_obj_1'
> ERROR: Process no longer exists
That's true, that crashes even for me. I still expected it crashes for you if
you remove the two lines:
if (classification == NAME)
break;
which cannot / does not crash.
> Jan> So I still believe those two lines
> Jan> if (classification == NAME)
> Jan> break;
> Jan> are just some cleanup/simplification but not required by this patch.
>
> Ok, I see what you mean, but the subsequent line is not valid for NAME:
>
> context_type = yylval.tsym.type;
OK, that makes sense now.
(It cannot crash but I agree it is not clean to read such data.)
> I guess you are saying I should invert the if.
> Ok, I will do that.
No, I did not mean that. In fact I do not understand much what condition
inversion do you mean.
I am fine with the patch now.
Thanks,
Jan
next prev parent reply other threads:[~2013-02-11 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 19:51 Tom Tromey
2013-02-03 5:45 ` Jan Kratochvil
2013-02-04 16:33 ` Tom Tromey
2013-02-04 21:47 ` Tom Tromey
2013-02-07 19:15 ` Jan Kratochvil
2013-02-11 20:28 ` Tom Tromey
2013-02-11 20:39 ` Jan Kratochvil [this message]
2013-02-11 20:45 ` Tom Tromey
2013-02-11 20:58 ` Jan Kratochvil
2013-02-12 20:20 ` 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=20130211203930.GA26149@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.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