From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com
Subject: [rfa/testsuite] gdb1250.exp: make 'break abort' work with new pending breakpoints
Date: Mon, 09 Feb 2004 07:23:00 -0000 [thread overview]
Message-ID: <20040209072340.665D84B104@berman.michael-chastain.com> (raw)
This patch enhances gdb.base/gdb1250.exp so that it works with
the new pending-breakpoint interface. This test wants to set a
breakpoint on 'abort', which may be in a shared library.
Of course it still works with the old 'just quietly set the breakpoint'
interface.
I tested on native i686-pc-linux-gnu, red hat 8.0, glibc 2.2.93-5-rh.
I tested with gdb 6.0 and gdb HEAD, gcc 3.3.2, binutils 2.14 and
binutils HEAD, dwarf-2 and stabs+. All the tests PASSed in all
configurations.
This test is sensitive to the version of binutils because binutils HEAD
has a PLT optimization for shared library functions.
Okay to commit?
Michael C
2004-02-09 Michael Chastain <mec.gnu@mindspring.com>
* gdb.base/gdb1250.exp: Improve 'break abort' to work with new
pending-breakpoint user interface.
Index: gdb1250.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/gdb1250.exp,v
retrieving revision 1.1
diff -c -3 -p -r1.1 gdb1250.exp
*** gdb1250.exp 15 Jul 2003 16:28:21 -0000 1.1
--- gdb1250.exp 9 Feb 2004 07:17:30 -0000
***************
*** 1,4 ****
! # Copyright 2003 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
--- 1,4 ----
! # Copyright 2003, 2004 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
*************** gdb_start
*** 42,51 ****
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
! if ![runto abort] then {
perror "couldn't run to breakpoint"
continue
}
# See http://sources.redhat.com/gdb/bugs/1250
#
--- 42,67 ----
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
! # Set a breakpoint on 'abort' and run to it. gdb_breakpoint and runto
! # do not work because they answer 'no' to the breakpoint-pending
! # question.
!
! if { ![runto_main] } then {
perror "couldn't run to breakpoint"
continue
}
+
+ gdb_test_multiple "break abort" "break on abort" {
+ -re "Breakpoint $decimal .*$gdb_prompt $" {
+ pass "break on abort"
+ }
+ -re "Function \"abort\" not defined.\r\n.*Make breakpoint pending on future shared library load? \\(y or n\\) $" {
+ send_gdb "yes\n"
+ exp_continue
+ }
+ }
+
+ gdb_test "continue" "Breakpoint $decimal.*" "continue to abort"
# See http://sources.redhat.com/gdb/bugs/1250
#
next reply other threads:[~2004-02-09 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 7:23 Michael Elizabeth Chastain [this message]
2004-02-09 15:38 ` Daniel Jacobowitz
2004-02-09 22:05 Michael Elizabeth Chastain
2004-02-09 22:33 ` Daniel Jacobowitz
2004-02-09 22:45 Michael Elizabeth Chastain
2004-02-09 22:51 ` Daniel Jacobowitz
2004-02-09 22:55 Michael Elizabeth Chastain
2004-02-29 17:42 ` Daniel Jacobowitz
2004-03-02 15:48 Michael Elizabeth Chastain
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-24 18:42 ` 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=20040209072340.665D84B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--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