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/29277] jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed with separate debug files Date: Mon, 01 Aug 2022 16:46:12 +0000 [thread overview] Message-ID: <bug-29277-4717-bwJVUjNSRH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29277-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29277 --- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> --- Reproduced with target board cc-with-gnu-debuglink.exp and test-case gdb.base/jit-reader.exp, and this trigger patch: ... diff --git a/gdb/contrib/cc-with-tweaks.sh b/gdb/contrib/cc-with-tweaks.sh index 7919d2da85a..ea064e6a564 100755 --- a/gdb/contrib/cc-with-tweaks.sh +++ b/gdb/contrib/cc-with-tweaks.sh @@ -267,7 +267,7 @@ if [ "$want_gnu_debuglink" = true ]; then debug_file="$tmpdir"/$(basename "$output_file").debug # Create stripped and debug versions of output_file. - strip --strip-debug "${output_file}" \ + strip --strip-all "${output_file}" \ -o "${stripped_file}" rc=$? [ $rc != 0 ] && exit $rc ... Note btw that with the fix we no longer run into the assert, but there are still plenty of fails in test-cases gdb.base/jit-*.exp. Maybe there are hardcoded assumptions in the test-cases about minimal symbols being present? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-01 16:46 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-22 19:20 [Bug breakpoints/29277] New: " guillaume at morinfr dot org 2022-06-23 13:44 ` [Bug breakpoints/29277] " vries at gcc dot gnu.org 2022-06-27 14:06 ` hector.oron at gmail dot com 2022-07-19 14:23 ` vries at gcc dot gnu.org 2022-08-01 13:46 ` schwab@linux-m68k.org 2022-08-01 15:55 ` vries at gcc dot gnu.org 2022-08-01 15:56 ` vries at gcc dot gnu.org 2022-08-01 16:46 ` vries at gcc dot gnu.org [this message] 2022-10-13 13:40 ` vries at gcc dot gnu.org 2023-12-16 15:24 ` ssbssa at sourceware dot org 2023-12-16 15:36 ` 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-29277-4717-bwJVUjNSRH@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).