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 94C5D3858C55; Sat,  7 May 2022 20:45:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 94C5D3858C55
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29128] "internal-error: find_pc_sect_compunit_symtab:
 Assertion `result != nullptr' failed" while debugging asm program
Date: Sat, 07 May 2022 20:45:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simark at simark dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29128-4717-aBit4fDQvy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29128-4717@http.sourceware.org/bugzilla/>
References: <bug-29128-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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 07 May 2022 20:45:22 -0000

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

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
(In reply to Tom Tromey from comment #2)
> gdb shouldn't crash here, but also this file is weird.
>=20
> The .debug_info says:
>=20
>  <0><b>: Abbrev Number: 1 (DW_TAG_compile_unit)
>     <c>   DW_AT_low_pc      : 0x4000b0
>     <14>   DW_AT_high_pc     : 0x4000b0
>=20
> and
>=20
>  <1><3c>: Abbrev Number: 2 (DW_TAG_subprogram)
>     <3d>   DW_AT_low_pc      : 0x4000b0
>=20
> (no high PC for the function)

Agreed, looks like bad debug info.

On Ubuntu 20.04, with NASM version 2.14.02, at least the CU's high pc is ri=
ght:

0x0000000b: DW_TAG_compile_unit
              DW_AT_low_pc [DW_FORM_addr]       (0x0000000000401000)
              DW_AT_high_pc [DW_FORM_addr]      (0x000000000040101e)

The original report on IRC was about GDB not showing the lines when steppin=
g.=20
The root cause must be this NASM bug.  I think it's ok to not produce good
results when working with the bad debug info, but ideally we wouldn't crash.

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