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 01:07:55 +0000 [thread overview]
Message-ID: <bug-29681-4717-ZysPtAhBD6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29681-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29681
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
When you say it crashes, are you talking about this?
17: (2106595) <-1060-stack-list-frames 0 1000
17: (2106628) ->1060^error,msg="Call Frame Instruction op 45 in vendor
extension space is not handled on this architecture."
That's the only abnormal thing I see, and that would prevent VSCode from
showing a stack trace.
According to the message, a DWARF CFI expression uses the 45 (0x2d)
vendor-specific operator. From your logs, I see that you are on AArch64
(ARM64), so it's probably
DW_CFA_AARCH64_negate_ra_state:
https://gitlab.com/gnutools/binutils-gdb/-/blob/091782c46d9b321f5b7c5e5330b5febe015d73d6/include/dwarf2.def#L791
I see that we handle it here:
https://gitlab.com/gnutools/binutils-gdb/-/blob/091782c46d9b321f5b7c5e5330b5febe015d73d6/gdb/aarch64-tdep.c#L1339
Looks like you are using GDB 8.3, which is too old. It looks like it was added
in GDB 9.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-14 1:07 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 [this message]
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
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-ZysPtAhBD6@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).