From: "Kévin Le Gouguec" <legouguec@adacore.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Guard against frame.c destructors running before frame-info.c's
Date: Tue, 15 Nov 2022 23:32:40 +0100 [thread overview]
Message-ID: <87h6yzalx3.fsf@adacore.com> (raw)
In-Reply-To: <4065164f-f473-1c9d-7b24-2420b00f47a3@polymtl.ca> (Simon Marchi's message of "Tue, 15 Nov 2022 16:57:32 -0500")
Simon Marchi <simon.marchi@polymtl.ca> writes:
> Do you have a way to reproduce, so we can experiment with it?
On our Windows machines, IIRC the internal error was triggered reliably
on every GDB exit; "IIRC" because at some point I started testing just
by running --version (which is what this backtrace corresponds to).
Let me know if more information about this configuration would help, or
if there are more tests I should run. FWIW that GDB was built with GCC
11.3.1 (+ a couple of AdaCore patches); --configuration says:
> This GDB was configured as follows:
> configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32
> --with-auto-load-dir=$debugdir:$datadir/auto-load
> --with-auto-load-safe-path=$debugdir:$datadir/auto-load
> --with-expat
> --with-gdb-datadir=[…] (relocatable)
> --with-jit-reader-dir=[…] (relocatable)
> --without-libunwind-ia64
> --with-lzma
> --without-babeltrace
> --without-intel-pt
> --with-mpfr
> --without-xxhash
> --with-python=[…]
> --with-python-libdir=[…]
> --without-debuginfod
> --without-guile
> --disable-source-highlight
> --enable-threading
> --with-separate-debug-dir=[…]
Thanks.
next prev parent reply other threads:[~2022-11-15 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 20:48 Kévin Le Gouguec
2022-11-15 21:57 ` Simon Marchi
2022-11-15 22:32 ` Kévin Le Gouguec [this message]
2022-11-16 1:03 ` Tom Tromey
2022-11-16 1:19 ` Simon Marchi
2022-11-16 7:05 ` Kévin Le Gouguec
2022-11-16 14:39 ` Simon Marchi
2022-11-16 16:25 ` Kévin Le Gouguec
2022-11-16 16:28 ` 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=87h6yzalx3.fsf@adacore.com \
--to=legouguec@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).