From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: help: dejagnu stumps me again
Date: Thu, 10 Jan 2002 10:11:00 -0000 [thread overview]
Message-ID: <20020110131220.A7323@nevyn.them.org> (raw)
In-Reply-To: <3C3DD566.2070803@cygnus.com>
On Thu, Jan 10, 2002 at 12:54:46PM -0500, Andrew Cagney wrote:
> >RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/demangle.exp,v
> >retrieving revision 1.1.1.4
> >diff -u -r1.1.1.4 demangle.exp
> >--- demangle.exp 1999/09/09 00:00:27 1.1.1.4
> >+++ demangle.exp 2002/01/10 03:42:29
> >@@ -531,7 +531,18 @@
> > test_demangling_exact "gnu:
> > foo__I_4000000000000000000000000000000000000000000000000000000000000000000000000" "Can't demangle \"foo__I_4000000000000000000000000000000000000000000000000000000000000000000000000\""
> >
> > ## 1999-04-19: "Fix from Dale Hawkins". Shouldn't segfault.
> >- test_demangling_exact "gnu:
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator" "Can't demangle \"__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator\""
> >+ # Accept even a dubious demangling; the string is ambiguous.
> >+ send_gdb "maintenance demangle
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator\n"
> >+ gdb_expect {
> >+ -ex "virtual function thunk (delta:-64) for
> >CosNaming::_proxy_NamingContext::_0RL__list(unsigned long,
> >_CORBA_Unbounded_Sequence<CosNaming::Binding> *&,
> >CosNaming::BindingIterator *&)"
> >+ { pass "gnu:
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator" }
> >+ -ex "Can't demangle
> >\"__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator\""
> >+ { pass "gnu:
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator" }
> >+ -re ".*$gdb_prompt $"
> >+ { fail "gnu:
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator" }
> >+ timeout
> >+ { fail "gnu:
> >__thunk_64__0RL__list__Q29CosNaming20_proxy_NamingContextUlRPt25_CORBA_Unbounded_Sequence1ZQ29CosNaming7BindingRPQ29CosNaming15BindingIterator (timeout)" }
> >+ }
> > }
> >
>
> An un anchored pattern such as ".*...." is bad. It sends expect into
> drug induced bliss while it tries to match everything.
>
> TCL is fun. expect well, deajgnu er ...
I don't see why it's a problem - that's how we match the prompt on all
the other gdb_expect blocks. I'll keep poking at it.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-01-10 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 19:47 Daniel Jacobowitz
2002-01-10 9:54 ` Andrew Cagney
2002-01-10 10:11 ` Daniel Jacobowitz [this message]
2002-01-10 11:47 ` Elena Zannoni
2002-01-13 14:04 ` Daniel Jacobowitz
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=20020110131220.A7323@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.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