From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix expected received signal message in testsuite
Date: Fri, 25 Nov 2022 11:04:08 +0100 [thread overview]
Message-ID: <yddbkovnyef.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87o7sw2sfd.fsf@redhat.com> (Andrew Burgess's message of "Thu, 24 Nov 2022 17:06:30 +0000")
Hi Andrew,
> So, to clarify this a little, the discrepancy seems to arise from
> lwp_to_thread, this is where we query libthread-db.
>
> Before this point, in sol_thread_target::wait, we call:
>
> ptid_t rtnval = beneath ()->wait (ptid, ourstatus, options);
>
> this returns us the (maybe?) expected ptid_t {m_pid = 7218, m_lwp = 1,
> m_tid = 0}, then when we call lwp_to_thread, we get back the alternative
> ptid_t where the tid field is set, but the lwp field is not.
>
> I don't know if this indicates a bug in libthread-db, or a bug in GDB.
I wouldn't suspect libthread_db itself, but rather the sol-thread.c
code. I guess I'll have to do a debug build of gdb and find what's
going on.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-11-25 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:04 Rainer Orth
2019-09-13 12:47 ` Rainer Orth
2019-09-13 22:18 ` Andrew Burgess
2022-11-22 9:18 ` Rainer Orth
2022-11-24 16:01 ` Andrew Burgess
2022-11-24 17:06 ` Andrew Burgess
2022-11-25 10:04 ` Rainer Orth [this message]
2022-11-25 9:58 ` Rainer Orth
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=yddbkovnyef.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=aburgess@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@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).