public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/27822] New: [gdb/tdep, x86_64] Wrong thread picked to select process 64/32-bitness Date: Tue, 04 May 2021 14:00:19 +0000 [thread overview] Message-ID: <bug-27822-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27822 Bug ID: 27822 Summary: [gdb/tdep, x86_64] Wrong thread picked to select process 64/32-bitness Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- See this conversation here ( https://lore.kernel.org/io-uring/CAHk-=wh0KoEZXPYMGkfkeVEerSCEF1AiCZSvz9TRrx=Kj74D+Q@mail.gmail.com/ ). The problem seems to be that gdb picks the wrong thread to select 32-bit/64-bit property for a process. AFAICT, this is done here in x86_linux_nat_target::read_description: ... /* GNU/Linux LWP ID's are process ID's. */ tid = inferior_ptid.lwp (); if (tid == 0) tid = inferior_ptid.pid (); /* Not a threaded program. */ ... It's not obvious to me from the discussion what is wrong with that. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-04 14:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 14:00 vries at gcc dot gnu.org [this message] 2021-05-04 14:02 ` [Bug tdep/27822] " bp at alien8 dot de 2021-05-04 15:26 ` vries at gcc dot gnu.org 2021-05-07 8:44 ` vries at gcc dot gnu.org 2021-05-23 8:08 ` cvs-commit at gcc dot gnu.org 2021-05-23 8:11 ` vries at gcc dot gnu.org
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-27822-4717@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: linkBe 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).