From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "akamath996@gmail.com" <akamath996@gmail.com>,
"tom@tromey.com" <tom@tromey.com>,
"simon.marchi@polymtl.ca" <simon.marchi@polymtl.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
SANGAMESH MALLAYYA <sangamesh.swamy@in.ibm.com>,
Aditya Kamath <Aditya.Kamath1@ibm.com>
Subject: Re: [PATCH 1/2] Fix asertion failure while analysing core files in AIX with terminated threads.
Date: Tue, 24 Mar 2026 12:00:58 +0000 [thread overview]
Message-ID: <7591a18ffa2b5f73c75d6081fabe46776fcd9c64.camel@de.ibm.com> (raw)
In-Reply-To: <20260324095213.46219-2-akamath996@gmail.com>
Aditya Vidyadhar Kamath <akamath996@gmail.com> wrote:
>If we analyse core files today in AIX ( few of them ) we get,
> regcache.c:432: internal-error: get_thread_regcache:
> Assertion `thread->state != THREAD_EXITED' failed.
>
>The reason being the aix-thread.c file where root cause is the
>sync_threadlists()
>function. When reading an AIX core file, threads are reported by
>libpthread library as being in PST_TERM (terminated) state, which
>is correct since process crashed. However, sync_threadlists() was
>calling delete_thread() for these terminated threads, marking them
>as THREAD_EXITED in GDBs internal state.
I guess the more fundamental question would be, do we even need
sync_threadlists() at all when debugging a core file? Here,
the list of threads can never change, so what is the point of
attempting to sync it? Does it work if you just never call
sync_threadlists() for core files (or have it return early)?
Bye,
Ulrich
next prev parent reply other threads:[~2026-03-24 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 9:52 Aditya Vidyadhar Kamath
2026-03-24 12:00 ` Ulrich Weigand [this message]
2026-03-24 12:43 ` Aditya Kamath
2026-03-24 13:42 ` Ulrich Weigand
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=7591a18ffa2b5f73c75d6081fabe46776fcd9c64.camel@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=simon.marchi@polymtl.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