espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-21 18:39:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

gdb/testsuite: fix FAIL in gdb.base/clear_non_user_bp.exp

Browse Source 
Tom and Simon feedback that there is a test failing in this commit:

  commit a5c69b1e49bae4d0dcb20f324cebb310c63495c6
  Date:   Sun Apr 17 15:09:46 2022 +0800

    gdb: fix using clear command to delete non-user breakpoints(PR cli/7161)

Then, I reproduced the same fail with Ubuntu 20.04 as Simon said, and I
fixed the nit in this patch.  The root of the problem is not correctly
matching the presentation of internal breakpoints.

In addition, as Pedro pointed out, the original testcase is not portable
in some methods, so this patch fixes this issue and some other
improvements.

Tested on x86_64 ubuntu 20.04.4 and openSUSE Tumbleweed(VERSION_ID="20220425").
This commit is contained in:
Enze Li
2022-04-27 21:12:27 +08:00
parent 36b124126b
commit 41b96eef5f
1 changed files with 48 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
gdb/testsuite/gdb.base/clear_non_user_bp.exp
View File

@ -16,17 +16,45 @@
# Regression test for PR gdb/7161. Test that GDB cannot delete non-user # Regression test for PR gdb/7161. Test that GDB cannot delete non-user
# breakpoints with clear command. # breakpoints with clear command.
proc get_maint_info_bp { var } { # get_maint_bp_addr num
global expect_out #
global gdb_prompt # Purpose:
# Get address of the specified internal breakpoint when using command
gdb_test_multiple "maint info break $var" "find address of internal bp $var" { # "maint info breakpoints $num".
-re ".*(0x\[0-9a-f\]+).*$gdb_prompt $" { #
# Parameter:
# The parameter "num" indicates the number of the internal breakpoint
# to get. Note that this parameter must be a negative number.
# E.g., -1 means that we're gonna get the first internal breakpoint.
#
# Return:
# Internal breakpoint address.
#
proc get_maint_bp_addr { num } {
gdb_test_multiple "maint info break $num" "find address of internal bp $num" {
-re -wrap ".*(0x\[0-9a-f\]+).*" {
return $expect_out(1,string) return $expect_out(1,string)
} }
timeout { }
perror "couldn't find address of $var" return ""
return "" }
# get_first_maint_bp_num
#
# Purpose:
# Get the first number of all internal breakpoints when using command
# "maint info breakpoints".
#
# Parameter:
# None.
#
# Return:
# Internal breakpoint number, which is negative.
#
proc get_first_maint_bp_num { } {
gdb_test_multiple "maint info break" "find first internal bp num" {
-re -wrap "(-\[0-9\]).*" {
return $expect_out(1,string)
} }
} }
return "" return ""
@ -48,17 +76,19 @@ if ![runto_main] then {
return 0 return 0
} }
gdb_test "break main.c:21" \ set bp_num [get_first_maint_bp_num]
".*Breakpoint.* at .*" \ set bp_addr [get_maint_bp_addr $bp_num]
"set breakpoint"
set bp_addr [get_maint_info_bp "-1"] gdb_test "maint info break $bp_num" \
"$bp_num.*$bp_addr.*" \
gdb_test "maint info break -1" \ "maint info breakpoint \$bp_num"
"-1.*shlib events.*keep y.*$bp_addr.*" \
"maint info breakpoint -1 error"
gdb_test "clear *$bp_addr" \ gdb_test "clear *$bp_addr" \
"No breakpoint at \\*$bp_addr." \ "No breakpoint at \\*$bp_addr." \
"clear internal breakpoint error" "clear internal breakpoint"
# Check again, make sure that GDB really didn't delete the internal breakpoint.
gdb_test "maint info break $bp_num" \
"$bp_num.*$bp_addr.*" \
"maint info breakpoint \$bp_num after clear"