Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: [RFC] delete gdb.cp/ambiguous.exp ?
Date: Mon, 18 Aug 2014 23:23:00 -0000	[thread overview]
Message-ID: <yjt27g25tmac.fsf@ruffy.mtv.corp.google.com> (raw)

Along the lines of dead code removal ...

What should we do with this testcase?

The messages it is looking for from gdb do not exist,
but the whole thing is not run for gcc anyway.

I ask because if we choose to not delete the testcase
then I will need to add a similar escape for clang.

# tests relating to ambiguous class members
# Written by Satish Pai <pai@apollo.hp.com> 1997-07-28

...

if { [test_compiler_info gcc-*] } then { continue }

...

# print out various class objects' members.  The values aren't
# important, just check that the warning is emitted at the
# right times. 

# X is derived from A1 and A2; both A1 and A2 have a member 'x'
send_gdb "print x.x\n"
gdb_expect {
   -re "warning: x ambiguous; using X::A2::x. Use a cast to disambiguate.\r\n\\$\[0-9\]* = \[-\]*\[0-9\]*\r\n$gdb_prompt $" {
       pass "print x.x"
   }
   -re "warning: x ambiguous; using X::A1::x. Use a cast to disambiguate.\r\n\\$\[0-9\]* = \[-\]*\[0-9\]*\r\n$gdb_prompt $" {
       pass "print x.x"
   }
   -re ".*$gdb_prompt $" { fail "print x.x" }
   timeout { fail "(timeout) print x.x" }
}


             reply	other threads:[~2014-08-18 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 23:23 Doug Evans [this message]
2014-08-19  6:58 ` Joel Brobecker
2014-08-19 16:49 ` Pedro Alves
2014-08-19 17:25   ` Doug Evans
2014-08-19 17:50     ` Pedro Alves
2014-08-19 20:10       ` Doug Evans
2014-08-19 21:47         ` Pedro Alves
2014-08-22 20:07           ` Doug Evans

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=yjt27g25tmac.fsf@ruffy.mtv.corp.google.com \
    --to=dje@google.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