Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Thu, 07 Feb 2013 19:15:00 -0000	[thread overview]
Message-ID: <20130207191514.GA24179@host2.jankratochvil.net> (raw)
In-Reply-To: <87fw1bzr8m.fsf@fleche.redhat.com>

On Mon, 04 Feb 2013 22:47:05 +0100, Tom Tromey wrote:
> Jan> I do not see there a regression; this does not mean much for c-exp.y.
> 
> Tom> I'll look.
> Tom> It may be more visible under valgrind.
> 
> For me it reliably fails the 'ptype':
> 
> (gdb) ptype gnu_obj_1::'~gnu_obj_1'
> Segmentation fault (core dumped)

I really have the full testsuite without regressions.  I do not see why it
crashes for you.  Tried on Fedora Rawhide, both with -lmcheck and without
-lmcheck.

This case gnu_obj_1::'~gnu_obj_1' does not get handled there as the parser
parses it as:
   $1 = token TYPENAME ()
   $2 = token COLONCOLON ()
   $3 = nterm name ()
and when it sees '~gnu_obj_1' classify_inner_name returns ERROR.

Without these two lines:
        if (classification == NAME)
          break;
the loop goes again, last_was_coloncolon == 0 in
      if (next.token == NAME && last_was_coloncolon)
So it just stores back the fetched next token
          /* We've reached the end of the name.  */
          VEC_safe_push (token_and_value, token_fifo, &next);
and also does "break;".

So I still believe those two lines
        if (classification == NAME)
          break;
are just some cleanup/simplification but not required by this patch.


Thanks,
Jan


  reply	other threads:[~2013-02-07 19:15 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 [this message]
2013-02-11 20:28         ` Tom Tromey
2013-02-11 20:39           ` Jan Kratochvil
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=20130207191514.GA24179@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