public inbox for
 help / color / mirror / Atom feed
From: Simon Marchi <>
To: tdevries <>, Tom Tromey <>
Subject: Re: [PATCH] Handle SIGSEGV in gdb selftests
Date: Fri, 13 Jan 2023 20:11:47 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/26/22 03:02, tdevries via Gdb-patches wrote:
> On 2022-12-16 16:11, Tom Tromey via Gdb-patches wrote:
>>>>>>> "Tom" == Tom de Vries <> 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 .
>> Thanks, I updated the commit message.
> I ran into this again, tried out the patch and checked that it fixes the problem.
> Thanks,
> - Tom

Hi both Toms,

I still see the issue on Ubuntu 22.04, when testing with the
native-extended-gdbserver board:

Thread 1 "xgdb" received signal SIGSEGV, Segmentation fault.
0x00007ffff6d828f2 in GC_find_limit_with_bound () from /usr/lib/x86_64-linux-gnu/
(gdb) FAIL: gdb.gdb/selftest.exp: xgdb is at prompt

The modified code looks like this:

        set test "xgdb is at prompt"
        gdb_test_multiple "continue" $test {
            -i "$inferior_spawn_id"
            -re "received signal SIGSEGV.* in GC_.*$gdb_prompt" {
                # Some versions of the GC used by Guile cause a SEGV
                # during stack probing.  Ignore this and carry on.
                send_gdb "continue\n"
            -re "$banner" {
                pass $test

Shouldn't the SIGSEGV -re be before the `-i $inferior_spawn_id`?
Otherwise we expect the "received signal SIGSEGV" message to come from
the debugged GDB, when it's the top GDB that will print it (like when
debugging any other test program).

I think we don't see the problem when testing with native because
the top and bottom GDBs share the same spawn id.


  reply	other threads:[~2023-01-14  1: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
2022-12-26  8:02     ` tdevries
2023-01-14  1:11       ` Simon Marchi [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).