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 testsuite/29325] New: [gdb/guile] Fails in gdb.gdb/{python-helper,selftest}.exp when building with guile (sigsegv in libgc1) Date: Thu, 07 Jul 2022 05:56:28 +0000 [thread overview] Message-ID: <bug-29325-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29325 Bug ID: 29325 Summary: [gdb/guile] Fails in gdb.gdb/{python-helper,selftest}.exp when building with guile (sigsegv in libgc1) Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- When building gdb with guile, I run into a bunch of testsuite failures: ... FAIL: gdb.gdb/python-helper.exp: start inner gdb (timeout) FAIL: gdb.gdb/python-helper.exp: loading test binary into inner GDB (got interactive prompt) FAIL: gdb.gdb/python-helper.exp: print integer from DWARF info FAIL: gdb.gdb/python-helper.exp: pretty print type->main_type for DWARF type FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again FAIL: gdb.gdb/python-helper.exp: print *type->main_type FAIL: gdb.gdb/selftest.exp: xgdb is at prompt FAIL: gdb.gdb/selftest.exp: send ^C to child process (timeout) FAIL: gdb.gdb/selftest.exp: send SIGINT signal to child process (timeout) FAIL: gdb.gdb/selftest.exp: send ^C to child process again (timeout) FAIL: gdb.gdb/selftest.exp: thread 1 (timeout) FAIL: gdb.gdb/selftest.exp: backtrace through signal handler (timeout) ... In more detail: ... Thread 1 "xgdb" received signal SIGSEGV, Segmentation fault.^M 0x00007ffff71f1aa3 in ?? () from /lib64/libgc.so.1^M (outer-gdb) FAIL: gdb.gdb/python-helper.exp: start inner gdb (timeout) ... This is actually documented behaviour ( https://hboehm.info/gc/debugging.html ). So there's nothing wrong with gdb. Building gdb with guile makes gdb "a program that uses libgc1". The same behaviour can be reproduced by debugging a simple: ... $ cat test.c #include "gc.h" int main (void) { GC_INIT (); return 0; } ... compiled like: ... $ gcc test.c -lgc ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-07 5:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-07 5:56 vries at gcc dot gnu.org [this message] 2022-07-07 5:58 ` [Bug testsuite/29325] " vries at gcc dot gnu.org 2022-07-07 6:16 ` vries at gcc dot gnu.org 2022-07-07 6:17 ` vries at gcc dot gnu.org 2022-12-16 16:09 ` tromey at sourceware dot org 2022-12-16 16:09 ` tromey at sourceware dot org 2022-12-27 17:22 ` cvs-commit at gcc dot gnu.org 2022-12-27 19:31 ` tromey at sourceware dot 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-29325-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: 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).