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] [gdb/guile] Fails in gdb.gdb/{python-helper,selftest}.exp when building with guile (sigsegv in libgc1)
Date: Thu, 07 Jul 2022 05:58:31 +0000	[thread overview]
Message-ID: <bug-29325-4717-C9Lb0MznIr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29325-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29325

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
We could update the test-case to continue when hitting the SIGSEGV.

The documented advise to deal with this suggests:
...
(gdb) handle SIGSEGV SIGBUS nostop noprint"
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-07-07  5:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  5:56 [Bug testsuite/29325] New: " vries at gcc dot gnu.org
2022-07-07  5:58 ` vries at gcc dot gnu.org [this message]
2022-07-07  6:16 ` [Bug testsuite/29325] " 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-C9Lb0MznIr@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).