From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Cc: Daniel Jacobowitz <drow@false.org>
Subject: [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted'
Date: Fri, 15 Apr 2005 23:38:00 -0000 [thread overview]
Message-ID: <200504151638.04458.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050414193642.GB19792@nevyn.them.org>
OK. this is in partial responce to:
http://sourceware.org/ml/gdb-patches/2005-04/msg00145.html
There were two problems with gdb.base/annota1.exp. This patch is only for the first one.
The problem here is that, in some architectures, a breakpoints in a shared object will be
adjusted once the shared object is loaded. This cause two messages not accounted
for by gdb.base/annota1.exp:
Breakpoint address adjusted from ....
Breakpoint <n> address previously adjusted from ...
-=# Paul #=-
--
2005-04-15 Paul Gilliam <pgilliam@us.ibm.com>
* gdb.base/annota1.exp : Deal with messages caused by breakpoints in
shared objects being adjusted.
Index: gdb.base/annota1.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
retrieving revision 1.16
diff -c -3 -p -r1.16 annota1.exp
*** gdb.base/annota1.exp 20 Jul 2004 00:24:41 -0000 1.16
--- gdb.base/annota1.exp 21 Sep 2004 20:42:29 -0000
*************** send_gdb "break printf\n"
*** 229,234 ****
--- 229,236 ----
gdb_expect {
-re "\r\n\032\032post-prompt\r\n\r\n\032\032breakpoints-invalid\r\nBreakpoint.*at $hex.*$gdb_prompt$" \
{ pass "breakpoint printf" }
+ -re "\r\n\032\032post-prompt\r\nwarning: Breakpoint address adjusted from $hex to $hex.\r\n\r\n\032\032breakpoints-invalid\r\nBreakpoint.*at $hex.*$gdb_prompt$" \
+ { pass "breakpoint printf"}
-re ".*$gdb_prompt$" { fail "break printf" }
timeout { fail "break printf (timeout)" }
}
*************** send_gdb "continue\n"
*** 240,245 ****
--- 242,249 ----
gdb_expect {
-re "\r\n\032\032post-prompt\r\nContinuing.\r\n\r\n\032\032starting\r\n\r\n\032\032frames-invalid\r\n\r\n\032\032breakpoint 3\r\n\r\nBreakpoint 3, \r\n\032\032frame-begin 0 $hex\r\n\r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n.*\032\032frame-end\r\n\r\n\032\032stopped\r\n$gdb_prompt$" \
{ pass "continue to printf" }
+ -re "\r\n\032\032post-prompt\r\nContinuing.\r\n\r\n\032\032starting\r\n\r\n\032\032frames-invalid\r\nwarning: Breakpoint 3 address previously adjusted from $hex to $hex.\r\n\r\n\032\032breakpoint 3\r\n\r\nBreakpoint 3, \r\n\032\032frame-begin 0 $hex\r\n\r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*.*\032\032frame-function-name\r\n.printf\r\n\032\032frame-args\r\n.*\032\032frame-end\r\n\r\n\032\032stopped\r\n$gdb_prompt$" \
+ { pass "continue to printf" }
-re ".*$gdb_prompt$" { fail "continue to printf" }
timeout { fail "continue to printf (timeout)" }
}
next prev parent reply other threads:[~2005-04-15 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:27 [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:03 ` [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc Paul Gilliam
2005-04-30 18:49 ` Daniel Jacobowitz
2005-05-28 23:42 ` Daniel Jacobowitz
2005-04-15 23:38 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp Paul Gilliam
2005-04-27 15:49 ` Daniel Jacobowitz
2005-04-27 20:02 ` Paul Gilliam
2005-04-15 23:38 ` Paul Gilliam [this message]
2005-04-27 15:43 ` [PATCH] Fixes testsuit/gdb.base/annota1.exp to deal with 'Breakpoint address adjusted' Daniel Jacobowitz
2005-04-27 21:47 ` [COMMIT] " Paul Gilliam
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=200504151638.04458.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@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