public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27313] New: Segfault in insert_catch_syscall
Date: Tue, 02 Feb 2021 07:08:59 +0000 [thread overview]
Message-ID: <bug-27313-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27313
Bug ID: 27313
Summary: Segfault in insert_catch_syscall
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I did a testsuite run with target board fission-dwp and this patch:
...
diff --git a/gdb/contrib/cc-with-tweaks.sh b/gdb/contrib/cc-with-tweaks.sh
index 2eda76a89c2..f097c70a265 100755
--- a/gdb/contrib/cc-with-tweaks.sh
+++ b/gdb/contrib/cc-with-tweaks.sh
@@ -230,7 +230,7 @@ if [ "$want_dwp" = true ]; then
$DWP -o "${output_file}.dwp" ${dwo_files} > /dev/null
rc=$?
[ $rc != 0 ] && exit $rc
- rm -f ${dwo_files}
+ rm -f ${dwo_files} ${output_file}.dwp
fi
fi
...
to test behaviour of gdb when it cannot find the debug info package.
I ran into this:
...
ERROR: GDB process no longer exists
GDB process exited with wait status 31362 exp9 0 0 CHILDKILLED SIGABRT SIGABRT
UNRESOLVED: gdb.base/catch-syscall.exp: with args noxml: program has called -1
...
which is reproducible on the command line like this:
...
$ gdb -batch outputs/gdb.base/catch-syscall/catch-syscall -ex start -ex "catch
syscall -1" -ex continue
warning: Could not find DWO CU
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/catch-syscall/catch-syscall0.dwo(0x3879e0cb34736ded)
referenced by CU at offset 0xc7 [in module
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/catch-syscall/catch-syscall]
Temporary breakpoint 1 at 0x4007e6: file
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/catch-syscall.c, line
49.
Temporary breakpoint 1, main () at
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/catch-syscall.c:49
49 char buf1[2] = "a";
Catchpoint 2 (syscall -1)
Aborted (core dumped)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-02 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 7:08 vries at gcc dot gnu.org [this message]
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
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@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: link
Be 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).