From: Simon Marchi via Gdb <gdb@sourceware.org>
To: psmith@gnu.org, Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Subject: Re: GDB 15/16 crashing in add_thread_silent()
Date: Tue, 18 Nov 2025 15:24:50 -0500 [thread overview]
Message-ID: <e7b92133-0397-4fa2-bbd4-ab9d891d7ef3@simark.ca> (raw)
In-Reply-To: <8c367ecdc19782c16d9631d62b26635200e849f8.camel@gnu.org>
On 11/18/25 2:30 PM, Paul Smith via Gdb wrote:
> On Tue, 2025-11-18 at 11:33 -0700, Tom Tromey wrote:
>>>>>>> "Paul" == Paul Smith via Gdb <gdb@sourceware.org> writes:
>>
>> [...]
>> Paul> So, there appears to be some difference in binutils where it can't
>> Paul> parse this core file properly...?
>>
>> Yes, interesting find.
>> Unfortunately the next step is probably to bisect binutils to find
>> the offending patch. Or I guess debug and try to find what's going
>> wrong.
>
> Yeah. Unfortunately I will need to gird myself for that and I have a
> lot of other things happening. Bisecting will be a big job since we're
> jumping from binutils 2.30 (known to work) to binutils 2.43 (known to
> not work).
>
> It's probably worthwhile making some effort at debugging, to try to
> narrow down the locations in the code to consider during bisecting. It
> looks like somehow we cannot determine the PID / TID properly in this
> core file in newer binutils, while the older binutils can still dig it
> out. Unfortunately I've never looked at any of this code before but
> hopefully it will be tractable.
>
> Maybe this weekend I can spend a bit of time on this.
The beauty of bisecting is that the number of steps grows logarthmically
with the number of commits, so it's not that long :). If you are
allowed to share the core file, I wouldn't mind giving it a try.
Bisecting stuff is one of my favorite pastimes.
Simo
next prev parent reply other threads:[~2025-11-18 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 18:56 Paul Smith via Gdb
2025-11-14 19:12 ` Simon Marchi via Gdb
2025-11-14 19:20 ` Paul Smith via Gdb
2025-11-14 19:25 ` Simon Marchi via Gdb
2025-11-14 19:38 ` Paul Smith via Gdb
2025-11-14 20:03 ` Simon Marchi via Gdb
2025-11-14 20:13 ` Tom Tromey
2025-11-14 20:29 ` Paul Smith via Gdb
2025-11-14 20:42 ` Paul Smith via Gdb
2025-11-18 18:33 ` Tom Tromey
2025-11-18 19:30 ` Paul Smith via Gdb
2025-11-18 20:24 ` Simon Marchi via Gdb [this message]
2025-11-24 16:36 ` Paul Smith via Gdb
2025-11-21 11:59 ` Tom de Vries via Gdb
2025-11-24 15:19 ` Paul Smith via Gdb
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=e7b92133-0397-4fa2-bbd4-ab9d891d7ef3@simark.ca \
--to=gdb@sourceware.org \
--cc=psmith@gnu.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/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