From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0378E3858C50; Thu, 7 Jul 2022 05:56:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0378E3858C50 From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2022 05:56:29 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29325 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.ht= ml ). 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 debuggi= ng a simple: ... $ cat test.c #include "gc.h" int main (void) { GC_INIT (); return 0; } ... compiled like: ... $ gcc test.c -lgc ... --=20 You are receiving this mail because: You are on the CC list for the bug.=