public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rajesh.palla at amd dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30825] New: GDB doesn't send Hg packet when switching the inferiors Date: Tue, 05 Sep 2023 10:54:34 +0000 [thread overview] Message-ID: <bug-30825-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30825 Bug ID: 30825 Summary: GDB doesn't send Hg packet when switching the inferiors Product: gdb Version: 12.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: rajesh.palla at amd dot com Target Milestone: --- When we switch the inferiors using infe command, I am expecting GDB to send Hg Packet to the remote stub so that the remote stub can work on the selected inferior. But GDB isn't sending the Hg packet every time. In a scenario where I have two inferiors, if I switch the inferiors without doing any operation, I don't see Hg Packet after first time infe 1 infe 2 infe 1 infe 2 Output log: GDB -> $Hgp1.1#af GDB <- $OK#9a GDB -> $g#67 GDB <- $0000000000e0030000.....#49 Is it expected to invalidate the pc register from regcache in <arch>_unwind_pc(). Because if I do so, it works but that will add more latency when we give step command etc..(it sends more g packets) Any solution? -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-09-05 10:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-05 10:54 rajesh.palla at amd dot com [this message] 2023-09-05 15:41 ` [Bug gdb/30825] " tromey at sourceware dot org 2023-09-06 4:29 ` rajesh.palla at amd dot com 2023-09-06 4:31 ` rajesh.palla at amd dot com 2023-09-06 16:38 ` tromey at sourceware dot 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-30825-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).