From: Tom Tromey <tromey@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle SIGSEGV in gdb selftests
Date: Fri, 16 Dec 2022 09:11:32 -0700 [thread overview]
Message-ID: <87pmcjba6j.fsf@tromey.com> (raw)
In-Reply-To: <7fca4280-a259-9785-fdd1-ac802b886804@suse.de> (Tom de Vries's message of "Fri, 16 Dec 2022 16:17:29 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> On 12/15/22 22:14, Tom Tromey via Gdb-patches wrote:
>> The gdb.gdb self-tests were timing out for me. Looking into it, the
>> problem is that the version of the Boehm GC that is used by Guile on
>> my machine causes a SEGV during stack probing. This unexpected stop
>> confuses the tests and causes repeated timeouts.
>>
Tom> FWIW, that's https://sourceware.org/bugzilla/show_bug.cgi?id=29325 .
Thanks, I updated the commit message.
Tom
next prev parent reply other threads:[~2022-12-16 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 21:14 Tom Tromey
2022-12-16 15:17 ` Tom de Vries
2022-12-16 16:11 ` Tom Tromey [this message]
2022-12-26 8:02 ` tdevries
2023-01-14 1:11 ` Simon Marchi
2023-01-14 1:19 ` Simon Marchi
2023-01-17 16:20 ` Tom Tromey
2023-01-17 16:22 ` Simon Marchi
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=87pmcjba6j.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).