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] GDB doesn't send Hg packet when switching the inferiors Date: Wed, 06 Sep 2023 04:29:59 +0000 [thread overview] Message-ID: <bug-30825-4717-MlZz7ULu8X@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30825-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30825 --- Comment #2 from Palla, Rajesh <rajesh.palla at amd dot com> --- This is the new target we added for AMD cores. pc_unwind function is similar to default pc_unwind() except that it invalidates the cache when there is a change in the inferior. static CORE_ADDR aiengine_unwind_pc (struct gdbarch *gdbarch, struct frame_info *next_frame) { gdb_byte buf[4]; struct inferior *inf = current_inferior (); if (inf->pid != prev_pid){ prev_pid = inf->pid; get_current_regcache()->invalidate(gdbarch_pc_regnum (gdbarch)); } frame_unwind_register (next_frame, gdbarch_pc_regnum (gdbarch), buf); return extract_typed_address (buf, builtin_type (gdbarch)->builtin_func_ptr); } Couple of questions: 1. When I tried to debug "arm arch", I see the Hg packets are sent every time we switch the inferior without doing any operation. (see log.txt attached) 2. In our case, I don't see Hg packet being sent lazily when we give 'c&' command. See the below log. But for other commands like mem read, I see Hg packet being sent. ----(gdb) infe 1 GDB -> $Hgp1.1#af GDB <- $OK#9a GDB -> $g#67 GDB <- $0000....#df ----(gdb) infe 2 ----(gdb) c & GDB -> $vCont;c:p2.-1#10 GDB <- $OK#9a ----(gdb) infe 1 ----(gdb) b producer GDB -> $m280,4#67 GDB <- $00000000#80 GDB -> $Z0,280,4#b0 GDB <- $OK#9a -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-06 4:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-05 10:54 [Bug gdb/30825] New: " rajesh.palla at amd dot com 2023-09-05 15:41 ` [Bug gdb/30825] " tromey at sourceware dot org 2023-09-06 4:29 ` rajesh.palla at amd dot com [this message] 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-MlZz7ULu8X@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).