public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "daniel.hilburn at outlook dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/29681] VS 2022 Preview C++ Android debugger crashes on breakpoint in thread on arm64v8a device Date: Fri, 14 Oct 2022 14:17:35 +0000 [thread overview] Message-ID: <bug-29681-4717-FZOXkLZaKT@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29681-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29681 --- Comment #8 from Daniel Hilburn <daniel.hilburn at outlook dot com> --- As I understand it Visual Studio has a gdb "frontend" (not sure what that means), so maybe that is it on my PC side of things. The Android NDK ships with a prebuilt gdbserver, which Visual Studio deploys with my application to the Android device. I thought that adb was communicating with that, but maybe it is Visual Studio itself. In trying to track down my local gdb file to update it, I debugged my application from Visual Studio and looked in Task Manager to see what programs were running. I saw adb but no gdb, so that's why I was thinking that VS was using adb. I'll look into how Visual Studio's gdb debugger works and see if I can track that down. Incidentally, do you think that the error is originating from the gdbserver on the device or from the gdb on my host PC? The way it emits seems like Visual Studio is sending a command to gdbserver to retrieve the callstack when the breakpoint hits and gdbserver is replying that the specified command is not handled. Does that correct? If so, that would imply that the host debugger in VS is more up-to-date than the gdbserver instance running on the device. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-14 14:17 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 13:54 [Bug threads/29681] New: " daniel.hilburn at outlook dot com 2022-10-13 14:01 ` [Bug threads/29681] " daniel.hilburn at outlook dot com 2022-10-13 14:01 ` daniel.hilburn at outlook dot com 2022-10-13 14:02 ` daniel.hilburn at outlook dot com 2022-10-14 1:07 ` simark at simark dot ca 2022-10-14 1:59 ` daniel.hilburn at outlook dot com 2022-10-14 13:19 ` daniel.hilburn at outlook dot com 2022-10-14 14:08 ` simark at simark dot ca 2022-10-14 14:17 ` daniel.hilburn at outlook dot com [this message] 2022-10-14 15:11 ` simark at simark dot ca 2022-10-14 15:30 ` daniel.hilburn at outlook dot com 2022-10-14 15:56 ` simark at simark dot ca 2022-10-14 16:07 ` daniel.hilburn at outlook dot com 2022-10-14 16:09 ` daniel.hilburn at outlook dot com 2022-10-15 14:12 ` daniel.hilburn at outlook dot com
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-29681-4717-FZOXkLZaKT@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).