From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFA: implement ambiguous linespec proposal
Date: Wed, 16 Nov 2011 15:43:00 -0000 [thread overview]
Message-ID: <4EC3DA13.4060907@codesourcery.com> (raw)
In-Reply-To: <m3vcqmpg0i.fsf@fleche.redhat.com>
On 11/15/2011 05:10 AM, Tom Tromey wrote:
> Tom> Here is a refresh of this patch. This fixes the regressions noted by
> Tom> Jan, but also changes ovsrch.exp not to assume that namespace lookups
> Tom> are done.
>
> Here is the final revision.
Tom,
I applied it to GDB CVS 2011-11-10, and run regression test on
tic6x-uclinux. There are two new fails,
-PASS: gdb.cp/ovsrch.exp: break outer::foo if (a == 3)
+FAIL: gdb.cp/ovsrch.exp: break A::outer::foo if (a == 3)
-PASS: gdb.cp/ovsrch.exp: break inner::foo if (a == 3)
+FAIL: gdb.cp/ovsrch.exp: break A::B::inner::foo if (a == 3)
break A::outer::foo if (a == 3)^M
Note: breakpoints 4, 5, 6, 7, 8 and 9 also set at pc 0xe79e2434.^M
Note: breakpoints 12, 13, 14, 15, 16 and 17 also set at pc 0xe79e23d4.^M
Note: breakpoints 10 and 11 also set at pc 0xe79e2370.^M
No symbol "a" in current context.^M
(gdb) FAIL: gdb.cp/ovsrch.exp: break A::outer::foo if (a == 3)
break A::B::inner::foo if (a == 3)^M
Note: breakpoints 20, 21, 22, 23, 24 and 25 also set at pc 0xe79e245c.^M
Note: breakpoints 28, 29, 30, 31, 32 and 33 also set at pc 0xe79e23fc.^M
Note: breakpoints 26 and 27 also set at pc 0xe79e2394.^M
No symbol "a" in current context.^M
(gdb) FAIL: gdb.cp/ovsrch.exp: break A::B::inner::foo if (a == 3)
I'll debug this problem tomorrow, but if you have any clues, that will
be helpful.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-11-16 15:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 17:34 Tom Tromey
2011-10-28 20:52 ` Matt Rice
2011-11-01 20:38 ` Tom Tromey
2011-10-28 22:41 ` Jan Kratochvil
2011-11-01 20:58 ` Tom Tromey
2011-11-03 20:49 ` Tom Tromey
2011-11-04 7:46 ` Jan Kratochvil
2011-11-08 16:36 ` Tom Tromey
2011-11-09 16:05 ` Joel Brobecker
2011-11-09 17:12 ` Tom Tromey
2011-11-09 17:56 ` Joel Brobecker
2011-11-09 18:19 ` Tom Tromey
2011-11-09 19:00 ` Joel Brobecker
2011-11-14 21:04 ` Tom Tromey
2011-11-14 21:32 ` Jerome Guitton
2011-11-09 18:37 ` Tom Tromey
2011-11-14 21:11 ` Tom Tromey
2011-11-15 16:30 ` Tom Tromey
2011-11-15 16:59 ` Pierre Muller
2011-11-16 0:09 ` Jan Kratochvil
2011-11-16 1:58 ` Joel Brobecker
2011-11-16 14:46 ` Tom Tromey
2011-11-18 14:10 ` Tom Tromey
2011-11-16 21:23 ` Stan Shebs
2011-11-16 2:28 ` Yao Qi
2011-11-16 3:20 ` Doug Evans
2011-11-16 14:46 ` Tom Tromey
2011-11-16 16:06 ` Tom Tromey
2011-11-16 4:57 ` Doug Evans
2011-11-16 5:22 ` Doug Evans
2011-11-16 14:54 ` Tom Tromey
2011-11-16 16:32 ` Doug Evans
2011-11-16 16:39 ` Tom Tromey
2011-11-16 14:49 ` Tom Tromey
2011-11-16 8:15 ` Yao Qi
2011-11-16 16:17 ` Tom Tromey
2011-11-16 15:43 ` Yao Qi [this message]
2011-11-16 16:11 ` Tom Tromey
2011-11-16 16:44 ` Tom Tromey
2011-11-17 3:49 ` Yao Qi
2011-11-21 21:50 ` Tom Tromey
2011-11-23 21:33 ` 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=4EC3DA13.4060907@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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