Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb <gdb@sourceware.org>
Cc: psmith@gnu.org,  Simon Marchi <simark@simark.ca>
Subject: Re: GDB 15/16 crashing in add_thread_silent()
Date: Fri, 14 Nov 2025 13:13:35 -0700	[thread overview]
Message-ID: <87seegtlsg.fsf@tromey.com> (raw)
In-Reply-To: <24d8355f-0233-4fbd-ac6e-8cda3f61916e@simark.ca> (Simon Marchi via Gdb's message of "Fri, 14 Nov 2025 15:03:40 -0500")

>>>>> "Simon" == Simon Marchi via Gdb <gdb@sourceware.org> writes:

>> Earlier if the PID couldn't be found then pid is set to CORELOW_PID
>> anyway, so this works and prevents the crash (although, I think GDB
>> should check for the nullptr return and do _something_ non-crashy...
>> maybe?)

Simon> I agree that part seems clearly buggy, but I don't think you should
Simon> focus on that.  The problem has already happened earlier in the
Simon> execution.

See this thread as well

https://inbox.sourceware.org/gdb-patches/20251024124208.1875651-1-tdevries@suse.de/

I wonder if the fix (assuming it arrives) should be in GDB 17.

Tom

  reply	other threads:[~2025-11-14 20:14 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 [this message]
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
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=87seegtlsg.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb@sourceware.org \
    --cc=psmith@gnu.org \
    --cc=simark@simark.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