public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/27313] Segfault in insert_catch_syscall Date: Fri, 05 Feb 2021 16:47:12 +0000 [thread overview] Message-ID: <bug-27313-4717-UTdezSA9EF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27313-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27313 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0e857c82883cff04ccc8868762c78b0e94ccde91 commit 0e857c82883cff04ccc8868762c78b0e94ccde91 Author: Tom de Vries <tdevries@suse.de> Date: Fri Feb 5 17:47:07 2021 +0100 [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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-05 16:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 7:08 [Bug breakpoints/27313] New: " vries at gcc dot gnu.org 2021-02-02 7:32 ` [Bug breakpoints/27313] " vries at gcc dot gnu.org 2021-02-02 8:14 ` vries at gcc dot gnu.org 2021-02-05 16:47 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-05 16:48 ` vries at gcc dot gnu.org
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=bug-27313-4717-UTdezSA9EF@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).