aboutsummaryrefslogtreecommitdiff
path: root/gdb/break-catch-syscall.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2021-02-05 17:47:07 +0100
committerTom de Vries <tdevries@suse.de>2021-02-05 17:47:07 +0100
commit0e857c82883cff04ccc8868762c78b0e94ccde91 (patch)
tree2da77697ed1016db5c8fadd40e36327f88d57085 /gdb/break-catch-syscall.c
parentbdfea17ea9bbd9f92ad19a70d770af42473d9c07 (diff)
downloadgdb-0e857c82883cff04ccc8868762c78b0e94ccde91.zip
gdb-0e857c82883cff04ccc8868762c78b0e94ccde91.tar.gz
gdb-0e857c82883cff04ccc8868762c78b0e94ccde91.tar.bz2
[gdb/breakpoints] Fix segfault for catch syscall -1
Using a hello world a.out, I run into a segfault: ... $ gcc hello.c $ gdb -batch a.out -ex "catch syscall -1" -ex r Catchpoint 1 (syscall -1) Aborted (core dumped) ... Fix this by erroring out if a negative syscall number is used in the catch syscall command. Tested on x86_64-linux. gdb/ChangeLog: 2021-02-05 Tom de Vries <tdevries@suse.de> PR breakpoints/27313 * break-catch-syscall.c (catch_syscall_split_args): Reject negative syscall numbers. gdb/testsuite/ChangeLog: 2021-02-05 Tom de Vries <tdevries@suse.de> PR breakpoints/27313 * gdb.base/catch-syscall.exp: Check that "catch syscall -1" is rejected.
Diffstat (limited to 'gdb/break-catch-syscall.c')
-rw-r--r--gdb/break-catch-syscall.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/break-catch-syscall.c b/gdb/break-catch-syscall.c
index 9772ac0..7335377 100644
--- a/gdb/break-catch-syscall.c
+++ b/gdb/break-catch-syscall.c
@@ -390,6 +390,8 @@ catch_syscall_split_args (const char *arg)
syscall_number = (int) strtol (cur_name, &endptr, 0);
if (*endptr == '\0')
{
+ if (syscall_number < 0)
+ error (_("Unknown syscall number '%d'."), syscall_number);
get_syscall_by_number (gdbarch, syscall_number, &s);
result.push_back (s.number);
}