Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] testsuite/gdb.c++/namespace-marker.exp: work around "marker() ()" bug
Date: Mon, 23 Apr 2001 06:09:00 -0000	[thread overview]
Message-ID: <3AE4292A.F19CD971@redhat.com> (raw)
In-Reply-To: <200104230630.XAA18353@bosch.cygnus.com>

Ditto.


Michael Elizabeth Chastain wrote:
> 
> This is Sunday Project Patch #10.
> 
> This patch changes testsuite/gdb.c++/namespace.exp to use the library
> function 'runto' to reach a marker function.  This simplifies the file,
> and it accommodates a bug in gdb when using g++ v3pre.
> 
> The bug is PR gdb/34, "g++ v3 functions show as "inheritance2() ()"".
> testsuite/gdb.c++/method.exp has one specific test case to detect this
> bug, so I want to fix other test scripts so that they don't cascade
> fail on this bug.
> 
> Before and after results with g++ v3pre:
>   before: 6 PASS, 5 FAIL
>   after:  9 PASS, 2 FAIL
> 
> I test this on native Red Hat Linux 7 and native Solaris 2.6 with
> gcc 2.95.3 and gcc 3pre dated 2001-04-22.
> 
> OK to apply?
> 
> Michael
> 
> ===
> 
> 2001-04-22  Michael Chastain  <chastain@redhat.com>
> 
>         * gdb.c++/namespace.exp: Use the 'runto' library function.
> 
> ===
> 
> Index: gdb/testsuite/gdb.c++/namespace.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/namespace.exp,v
> retrieving revision 1.5
> diff -c -3 -p -r1.5 namespace.exp
> *** gdb/testsuite/gdb.c++/namespace.exp 2001/03/08 21:09:23     1.5
> --- gdb/testsuite/gdb.c++/namespace.exp 2001/04/23 06:21:48
> *************** if ![runto_main] then {
> *** 68,87 ****
>       continue
>   }
> 
> ! send_gdb "break marker1\n" ; gdb_expect -re ".*$gdb_prompt $"
> !     send_gdb "cont\n"
> !     gdb_expect {
> !         -re "Break.* marker1 \\(\\) at .*:$decimal.*$gdb_prompt $" {
> !             send_gdb "up\n"
> !             gdb_expect {
> !                 -re ".*main.*$gdb_prompt $" { pass "up from marker1" }
> !                 -re ".*$gdb_prompt $"       { fail "up from marker1" }
> !                 timeout { fail "up from marker1 (timeout)" }
> !             }
> !         }
> !         -re "$gdb_prompt $" { fail "continue to marker1"  }
> !         timeout { fail "(timeout) continue to marker1"  }
> !     }
> 
>   # Access a data item inside a namespace using colons and
>   # single quotes :-(
> --- 68,79 ----
>       continue
>   }
> 
> ! if ![runto 'marker1'] then {
> !     perror "couldn't run to marker1"
> !     continue
> ! }
> !
> ! gdb_test "up" ".*main.*" "up from marker1"
> 
>   # Access a data item inside a namespace using colons and
>   # single quotes :-(

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


      reply	other threads:[~2001-04-23  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22 23:30 Michael Elizabeth Chastain
2001-04-23  6:09 ` Fernando Nasser [this message]

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=3AE4292A.F19CD971@redhat.com \
    --to=fnasser@redhat.com \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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