From: Fred Fish <fnf@specifix.com>
To: gdb-patches@sourceware.org
Cc: fnf@specifix.com
Subject: [PATCH] Recognize and skip interpreter_p initialization in selftest.exp
Date: Sun, 26 Feb 2006 18:40:00 -0000 [thread overview]
Message-ID: <200602261335.28612.fnf@specifix.com> (raw)
With the latest development gcc and latest development gdb,
selftest.exp fails because the breakpoint at captured_main gets set at
the interpreter_p initialization, which isn't currently one of the
recognized patterns. Apparently optimization has gotten better and
this code has been moved up the instruction stream:
(gdb) br captured_main
Breakpoint 1 at 0x807c714: file /src/latest/trunk/src/gdb/gdb/main.c, line 241.
(gdb) run
Starting program: /links/build/latest/trunk/i686-pc-linux-gnu/gdb/gdb/gdb
Breakpoint 1, captured_main (data=0xbfdbb3f4) at /src/latest/trunk/src/gdb/gdb/main.c:241
241 interpreter_p = xstrdup (context->interpreter_p);
-Fred
2006-02-26 Fred Fish <fnf@specifix.com>
* gdb.gdb/selftest.exp (do_steps_and_nexts): Recognize
and skip over interpreter_p initialization.
Index: testsuite/gdb.gdb/selftest.exp
===================================================================
RCS file: /cvsroots/latest/src/gdb/gdb/testsuite/gdb.gdb/selftest.exp,v
retrieving revision 1.1.1.2
diff -c -p -r1.1.1.2 selftest.exp
*** testsuite/gdb.gdb/selftest.exp 30 Dec 2005 18:53:28 -0000 1.1.1.2
--- testsuite/gdb.gdb/selftest.exp 26 Feb 2006 18:27:34 -0000
*************** proc do_steps_and_nexts {} {
*** 184,189 ****
--- 184,193 ----
set description "next over getcwd"
set command "next"
}
+ -re ".*interpreter_p = xstrdup.*$gdb_prompt $" {
+ set description "next over interpreter_p initialization"
+ set command "next"
+ }
-re "\[ \t\]+\{\r\n$gdb_prompt $" {
setup_xfail "mips-*-irix5*"
fail "$description ended up at odd location"
next reply other threads:[~2006-02-26 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 18:40 Fred Fish [this message]
2006-02-26 18:49 ` Daniel Jacobowitz
2006-02-26 19:38 ` Fred Fish
2006-02-26 20:23 ` Mark Kettenis
2006-02-26 22:44 ` 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=200602261335.28612.fnf@specifix.com \
--to=fnf@specifix.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