public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/24457] Segfault during gdb.execute('quit') within exit event handler
Date: Sat, 16 Dec 2023 14:50:53 +0000	[thread overview]
Message-ID: <bug-24457-4717-QGgBb8dOVQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24457-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24457

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |11.1
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Hannes Domani from comment #1)
> I can reproduce a problem with gdb 10.2:
> 
> C:/src/repos/binutils-gdb.git/gdb/thread.c:95: internal-error: thread_info*
> inferior_thread(): Assertion `current_thread_ != nullptr' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) y
> 
> But with 11.1 it works for me.
> 
> I think it was fixed by:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;
> h=219f56b4842f4e72540082af96e47efa0f0f0a82

I'm closing this now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-12-16 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24457-4717@http.sourceware.org/bugzilla/>
2022-01-05 16:20 ` ssbssa at sourceware dot org
2023-12-16 14:50 ` ssbssa at sourceware dot org [this message]

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=bug-24457-4717-QGgBb8dOVQ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).