From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 8A0FA385780D; Fri, 14 Oct 2022 01:07:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A0FA385780D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1665709676;
	bh=F5YlPb0bbxxKD5mSBEERhNTDOE03tjFm2uzUgx93jO8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=h3Y2LStgn7P6fG5CtJI8A0NeFxYKIFOxKisjjUzhEGcxGYaHGueEtoUYQlikLhXRE
	 H8Sgglk15U4gXz4UZAkUHjZzHVgq4kqoB80mig/J8W1iXIZrZYlMcN5sLFzQ4hwkO0
	 q6A4xhzwMFznLkxH9vlyJKLWROIp5SCsL1qhpN2g=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: threads
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-29681-4717-ZysPtAhBD6@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29681-4717@http.sourceware.org/bugzilla/>
References: <bug-29681-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29681

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=3D"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/091782c46d9b321f5b7c5e5330b=
5febe015d73d6/include/dwarf2.def#L791

I see that we handle it here:
https://gitlab.com/gnutools/binutils-gdb/-/blob/091782c46d9b321f5b7c5e5330b=
5febe015d73d6/gdb/aarch64-tdep.c#L1339

Looks like you are using GDB 8.3, which is too old.  It looks like it was a=
dded
in GDB 9.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=