[Bug breakpoints/27313] Segfault in insert_catch_syscall

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=27313

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
In more detail:
...
Thread 1 "gdb" received signal SIGSEGV, Segmentation fault.
0x00000000004ce250 in insert_catch_syscall (bl=0x2133960)
    at /home/vries/gdb_versions/devel/src/gdb/break-catch-syscall.c:98
98                ++inf_data->syscalls_counts[iter];
...
and the segfault happens because:
...
(gdb) p iter
$1 = -1
(gdb) p inf_data->syscalls_counts
$2 = std::vector of length 0, capacity 0
...

Tentative patch:
...
diff --git a/gdb/break-catch-syscall.c b/gdb/break-catch-syscall.c
index 9772ac01497..7335377f899 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);
        }
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.