public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <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:08:53 +0000 [thread overview]
Message-ID: <bug-29681-4717-8fyXd0nyaW@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 #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Daniel Hilburn from comment #6)
> In attempting to update my gdb version, it appears that Visual Studio's
> Android debugger is adb and it uses gdbserver deployed to the device with
> the deployed app to debug it remotely. Where did you see my gdb version
> information? I'd like to also check the gdbserver and adb versions to make
> sure that they are also up-to-date.
In your MI logs:
17: (2094895) ->~"GNU gdb (GDB) 8.3\n"
adb is the tool used to access / connect to devices, but you definitely have a
GDB somewhere. Any idea where it comes from, Android SDK or shipped with a
Visual Studio extension?
--
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:08 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 [this message]
2022-10-14 14:17 ` daniel.hilburn at outlook dot com
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-8fyXd0nyaW@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: 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).