OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
binutils-gdb/gdb/testsuite/gdb.base/save-bp.exp

88 lines
3.1 KiB
Plaintext
Raw Normal View History

Update Copyright year range in all files maintained by GDB.
2014-01-01 04:54:24 +01:00
# Copyright (C) 2011-2014 Free Software Foundation, Inc.
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
#
# 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
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
test suite update - gdb.base/s* Convert files gdb.base/s*.exp to use standard_output_file et al. * gdb.base/save-bp.exp, gdb.base/savedregs.exp, gdb.base/scope.exp, gdb.base/sep.exp, gdb.base/sepsymtab.exp, gdb.base/set-lang-auto.exp, gdb.base/setshow.exp, gdb.base/setvar.exp, gdb.base/shlib-call.exp, gdb.base/shreloc.exp, gdb.base/sigall.exp, gdb.base/sigaltstack.exp, gdb.base/sigbpt.exp, gdb.base/sigchld.exp, gdb.base/siginfo-addr.exp, gdb.base/siginfo-infcall.exp, gdb.base/siginfo-obj.exp, gdb.base/siginfo.exp, gdb.base/signals.exp, gdb.base/signest.exp, gdb.base/signull.exp, gdb.base/sigrepeat.exp, gdb.base/sigstep.exp, gdb.base/sizeof.exp, gdb.base/skip-solib.exp, gdb.base/so-impl-ld.exp, gdb.base/solib-display.exp, gdb.base/solib-nodir.exp, gdb.base/solib-overlap.exp, gdb.base/solib-symbol.exp, gdb.base/solib-weak.exp, gdb.base/source.exp, gdb.base/stack-checking.exp, gdb.base/stale-infcall.exp, gdb.base/stap-probe.exp, gdb.base/start.exp, gdb.base/step-break.exp, gdb.base/step-bt.exp, gdb.base/step-line.exp, gdb.base/step-resume-infcall.exp, gdb.base/step-test.exp, gdb.base/structs.exp, gdb.base/structs2.exp, gdb.base/structs3.exp, gdb.base/symbol-without-target_section.exp: Use standard_testfile, standard_output_file, prepare_for_testing, clean_restart.
2013-06-27 20:58:28 +02:00
standard_testfile .c
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
test suite update - gdb.base/s* Convert files gdb.base/s*.exp to use standard_output_file et al. * gdb.base/save-bp.exp, gdb.base/savedregs.exp, gdb.base/scope.exp, gdb.base/sep.exp, gdb.base/sepsymtab.exp, gdb.base/set-lang-auto.exp, gdb.base/setshow.exp, gdb.base/setvar.exp, gdb.base/shlib-call.exp, gdb.base/shreloc.exp, gdb.base/sigall.exp, gdb.base/sigaltstack.exp, gdb.base/sigbpt.exp, gdb.base/sigchld.exp, gdb.base/siginfo-addr.exp, gdb.base/siginfo-infcall.exp, gdb.base/siginfo-obj.exp, gdb.base/siginfo.exp, gdb.base/signals.exp, gdb.base/signest.exp, gdb.base/signull.exp, gdb.base/sigrepeat.exp, gdb.base/sigstep.exp, gdb.base/sizeof.exp, gdb.base/skip-solib.exp, gdb.base/so-impl-ld.exp, gdb.base/solib-display.exp, gdb.base/solib-nodir.exp, gdb.base/solib-overlap.exp, gdb.base/solib-symbol.exp, gdb.base/solib-weak.exp, gdb.base/source.exp, gdb.base/stack-checking.exp, gdb.base/stale-infcall.exp, gdb.base/stap-probe.exp, gdb.base/start.exp, gdb.base/step-break.exp, gdb.base/step-bt.exp, gdb.base/step-line.exp, gdb.base/step-resume-infcall.exp, gdb.base/step-test.exp, gdb.base/structs.exp, gdb.base/structs2.exp, gdb.base/structs3.exp, gdb.base/symbol-without-target_section.exp: Use standard_testfile, standard_output_file, prepare_for_testing, clean_restart.
2013-06-27 20:58:28 +02:00
if { [prepare_for_testing ${testfile}.exp ${testfile} $srcfile] } {
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
return -1
}
if ![runto_main] {
untested ${testfile}.exp
return -1
}
# Delete all breakpoints so that the "runto_main" breakpoint above
# does not interfere with our testing.
delete_breakpoints
# Insert a bunch of breakpoints... The goal is to create breakpoints
# that we are going to try to save in a file and then reload. So
# try to create a good variety of them.
gdb_breakpoint "break_me"
set loc_bp2 [gdb_get_line_number "BREAK HERE"]
gdb_breakpoint ${srcfile}:${loc_bp2}
set loc_bp3 [gdb_get_line_number "thread-specific"]
gdb_breakpoint "${srcfile}:${loc_bp3} thread 1"
set loc_bp4 [gdb_get_line_number "condition"]
gdb_breakpoint "${srcfile}:${loc_bp4} if i == 1"
set loc_bp5 [gdb_get_line_number "with commands"]
gdb_breakpoint ${srcfile}:${loc_bp5}
gdb_test "commands\nsilent\nend" "End with.*" "add breakpoint commands"
2013-04-23 Hui Zhu <hui@codesourcery.com> PR gdb/15165 * breakpoint.c (dprintf_print_recreate): New. (save_breakpoints): Let it not save dprintf commands. (initialize_breakpoint_ops): Set dprintf_print_recreate. 2013-04-23 Hui Zhu <hui@codesourcery.com> PR gdb/15165 * gdb.base/save-bp.exp: Add test for dprintf.
2013-04-23 04:42:44 +02:00
gdb_test "dprintf ${srcfile}:${loc_bp5},\"At foo entry\\n\"" "Dprintf .*"
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
# Now, save the breakpoints into a file...
simple changes in gdb.base This makes more changes in gdb.base to make it parallel-safe. I think the changes in this particular patch are relatively straightforward, so I've grouped them all together. 2013-11-04 Tom Tromey <tromey@redhat.com> * gdb.base/advance.exp: Use standard_testfile and prepare_for_testing. * gdb.base/bigcore.exp: Use standard_output_file. "cd" to appropriate directory when local. * gdb.base/dump.exp: Use standard_output_file. Update all "dump" and "restore" filenames. * gdb.base/interact.exp: Use standard_output_file. * gdb.base/jit-so.exp: Don't download file when local. * gdb.base/jit.exp (compile_jit_test): Don't download file when local. * gdb.base/list.exp: Use gdb_remote_download. * gdb.base/maint.exp: Use standard_output_file. * gdb.base/prelink.exp: Use standard_output_file. * gdb.base/save-bp.exp: Use standard_output_file. * gdb.base/sepdebug.exp: Use standard_testfile, standard_output_file. (test_different_dir): Don't declare objdir. * gdb.base/solib-search.exp: Use standard_output_file. * gdb.base/step-line.exp: Use gdb_remote_download. * gdb.base/trace-commands.exp: Use standard_output_file.
2013-08-23 20:18:01 +02:00
if {[is_remote host]} {
set bps bps
} else {
set bps [standard_output_file bps]
}
remote_file host delete "$bps"
gdb_test "save breakpoint $bps" "" "save breakpoint bps"
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
# Now start a new debugger session...
clean_restart $testfile
if ![runto_main] {
fail "cannot restart program"
return -1
}
# Delete all breakpoints so that the "runto_main" breakpoint above
# does not interfere with our testing.
delete_breakpoints
# ... and restore the breakpoints.
simple changes in gdb.base This makes more changes in gdb.base to make it parallel-safe. I think the changes in this particular patch are relatively straightforward, so I've grouped them all together. 2013-11-04 Tom Tromey <tromey@redhat.com> * gdb.base/advance.exp: Use standard_testfile and prepare_for_testing. * gdb.base/bigcore.exp: Use standard_output_file. "cd" to appropriate directory when local. * gdb.base/dump.exp: Use standard_output_file. Update all "dump" and "restore" filenames. * gdb.base/interact.exp: Use standard_output_file. * gdb.base/jit-so.exp: Don't download file when local. * gdb.base/jit.exp (compile_jit_test): Don't download file when local. * gdb.base/list.exp: Use gdb_remote_download. * gdb.base/maint.exp: Use standard_output_file. * gdb.base/prelink.exp: Use standard_output_file. * gdb.base/save-bp.exp: Use standard_output_file. * gdb.base/sepdebug.exp: Use standard_testfile, standard_output_file. (test_different_dir): Don't declare objdir. * gdb.base/solib-search.exp: Use standard_output_file. * gdb.base/step-line.exp: Use gdb_remote_download. * gdb.base/trace-commands.exp: Use standard_output_file.
2013-08-23 20:18:01 +02:00
gdb_test "source $bps" "" "source bps"
thread-specific breakpoints not saved properly by save-breakpoint Initially, I noticed that the save command was often missing new lines in the file that it generated. For instance, consider: % gdb save-bp (gdb) b break_me (gdb) b save-bp.c:27 (gdb) save breakpoints bps The contents of the bps file would be: % cat bps break break_mebreak save-bp.c:27 Looking further into the problem, I realized that the missing newlines are just a consequence of a missing call to print_recreate_thread. After having generated the breakpoint location in the break command, we cannot put a new line until we have looked at whether we need to add a 'thread NUM' argument. gdb/ChangeLog: * breakpoint.c (bkpt_print_recreate): Add call to print_recreate_thread. gdb/testsuite/ChangeLog: * gdb.base/save-bp.exp, gdb.base/save-bp.c: New files.
2011-10-02 04:13:13 +02:00
# Now, verify that all breakpoints have been created correctly...
set bp_row_start "\[0-9\]+ +breakpoint +keep +y +0x\[0-9a-f\]+ +in"
2013-04-23 Hui Zhu <hui@codesourcery.com> PR gdb/15165 * breakpoint.c (dprintf_print_recreate): New. (save_breakpoints): Let it not save dprintf commands. (initialize_breakpoint_ops): Set dprintf_print_recreate. 2013-04-23 Hui Zhu <hui@codesourcery.com> PR gdb/15165 * gdb.base/save-bp.exp: Add test for dprintf.
2013-04-23 04:42:44 +02:00
set dprintf_row_start "\[0-9\]+ +dprintf +keep +y +0x\[0-9a-f\]+ +in"
Use gdb_test_sequence in gdb.base/save-bp.exp. But IMO it is a functionality regression as: * gdb_test_sequence permits arbitary number of lines of text between those lines being matched. Former regex string did not allow it. This may make a difference if GDB regresses by printing some unexpected line after the breakpoint info line (like a "silent" line). > * \[\r\n\]+ can be used to anchor the beginning of the pattern, in the sense > of Perl regex ^ /m match. At least I have found such cases in existing > *.exp files so I used that. Using ^ really does not work. > > But I am not aware how to do Perl regex $ /m match. Using $ really does > not work. But this means that for example the trailing > ( \\((host|target) evals\\))? > on the line > "\[\r\n\]+\[ \t\]+stop only if i == 1( \\((host|target) evals\\))?" > originally made sense there but now it can be removed as it has no longer > any functionality there - it will match now any trailing line garbage. by Yao Qi: In this test case, ( \\((host|target) evals\\))? isn't needed in the pattern. What we test here is to save breakpoints into file and restore them from file. The contents saved in file are: break save-bp.c:31 condition $bpnum i == 1 the information about the place where the condition is evaluated isn't saved, so we don't need to check. Breakpoint save and restore has nothing to do with where the condition is evaluated (host or target). I am fine to leave it here now. gdb/testsuite/ChangeLog 2014-10-09 Jan Kratochvil <jan.kratochvil@redhat.com> * gdb.base/save-bp.exp (info break): Use gdb_test_sequence.
2014-10-12 21:47:13 +02:00
gdb_test_sequence "info break" "info break" [list \
"\[\r\n\]+Num +Type +Disp +Enb +Address +What" \
"\[\r\n\]+$bp_row_start break_me at \[^\r\n\]*$srcfile:\[0-9\]+" \
"\[\r\n\]+$bp_row_start main at \[^\r\n\]*$srcfile:$loc_bp2" \
"\[\r\n\]+$bp_row_start main at \[^\r\n\]*$srcfile:$loc_bp3 +thread 1" \
"\[\r\n\]+\[ \t]+stop only in thread 1" \
"\[\r\n\]+$bp_row_start main at \[^\r\n\]*$srcfile:$loc_bp4" \
"\[\r\n\]+\[ \t\]+stop only if i == 1( \\((host|target) evals\\))?" \
"\[\r\n\]+$bp_row_start main at \[^\r\n\]*$srcfile:$loc_bp5" \
"\[\r\n\]+\[ \t\]+silent" \
"\[\r\n\]+$dprintf_row_start main at \[^\r\n\]*$srcfile:$loc_bp5" \
"\[\r\n\]+\[ \t\]+printf" \
]