From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: help: dejagnu stumps me again
Date: Wed, 09 Jan 2002 19:47:00 -0000 [thread overview]
Message-ID: <20020109224807.A24112@nevyn.them.org> (raw)
I'm really not fond of TCL...
If someone could tell me the problem with the following patch, I'd be deeply
in their debt. I've spent several hours on this and the companion (failure
of the ^C handling in annota2.exp, which can be cured by putting a "shell
echo" in front of it. I've no idea if GDB or Expect is at fault and I can't
figure it out. My suspicion is GDB.)
This patch causes the testsuite to hang for a while. After it times out,
both the sent message and expected response appear. Changing -ex to -re
makes no difference.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
Index: demangle.exp
===================================================================
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)" }
+ }
}
#
next reply other threads:[~2002-01-10 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 19:47 Daniel Jacobowitz [this message]
2002-01-10 9:54 ` Andrew Cagney
2002-01-10 10:11 ` Daniel Jacobowitz
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=20020109224807.A24112@nevyn.them.org \
--to=drow@mvista.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