From: Simon Marchi <simark@simark.ca>
To: Bratislav Filipovic <bfilipov@amd.com>, bratislav.filipovic@amd.com
Cc: gdb-patches@sourceware.org, simon.marchi@efficios.com, tdevries@suse.de
Subject: Re: [PATCH] dwarf2: avoid decoding .debug_line for type units
Date: Thu, 23 Apr 2026 13:42:45 -0400 [thread overview]
Message-ID: <ee9b6075-0b39-46b0-979b-fa45c535df3f@simark.ca> (raw)
In-Reply-To: <20260423163752.3240149-1-bfilipov@amd.com>
On 4/23/26 12:37 PM, Bratislav Filipovic wrote:
> Running gdb.dwarf2/pr13961.exp with clang fails with an internal error:
>
> gdb/dwarf2/read.c: internal-error: decode_line_header_for_cu:
> Assertion `!cu->per_cu->is_debug_types ()' failed.
>
> pr13961 is a legacy .S test that references a .debug_line label from
> both a CU and a TU. The assembly includes an empty .debug_line section
> declaration:
>
> .section .debug_line,"",%progbits
> .Ldebug_line0:
>
> With gcc this results in a dummy (valid, but content-less) .debug_line
> header being emitted, so GDB can build a line header and resolve file
> indices. With clang the .debug_line section can be missing/empty,
> leaving the line header unset.
>
> During symbol creation, new_symbol may then try to lazily decode the
> CU-only line header while processing a type unit, which triggers the
> assertion above.
>
> Fix this by only decoding the line header for non-type units. If no
> line header is available, emit a complaint and continue without setting
> the symtab rather than attempting CU-only line decoding from a TU.
>
> Tested: gdb.dwarf2/pr13961.exp (CC_FOR_TARGET=clang-23)
There are some whitespace issues. I would suggest setting up pre-commit
and running it:
$ pre-commit run --all-files
...
check-whitespace.........................................................Failed
- hook id: check-whitespace
- exit code: 2
gdb/dwarf2/read.c:15433: indent with spaces.
+ struct symbol *sym)
gdb/dwarf2/read.c:15440: indent with spaces.
+ cu);
gdb/dwarf2/read.c:15447: indent with spaces.
+ &file_cu);
In fact, those warnings are about lines that shouldn't be changed by
this patch.
> @@ -15452,16 +15452,27 @@ new_symbol_file_line (struct die_info *die, struct dwarf2_cu *cu,
> if (!index_cst.has_value ())
> return;
>
> - if (file_cu->line_header == nullptr)
> + /* decode_line_header_for_cu is CU-only and asserts on debug_types.
> + For type units, the TU setup code runs before processing child DIEs,
> + so if line_header is still nullptr here it means there is no usable
> + line table for this unit. */
Just a small suggestion to be more precise and less repetitive:
/* decode_line_header_for_cu is CU-only and asserts on type units.
For type units, the line header setup runs before processing child
DIEs, in method dwarf2_cu::setup_type_unit_groups. So if
line_header is still nullptr here it means there is no usable line
table for this unit. */
With those fixed, the patch LGTM.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2026-04-23 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 13:35 Bratislav Filipovic
2026-04-01 14:54 ` [PING][PATCH] " Filipovic, Bratislav
2026-04-16 14:10 ` [PATCH] testsuite: ada-valprint-error relocation issue Bratislav Filipovic
2026-04-16 15:14 ` Tom de Vries
2026-04-20 13:16 ` [PATCH][PING] dwarf2: avoid decoding .debug_line for type units Filipovic, Bratislav
2026-04-23 16:37 ` [PATCH] " Bratislav Filipovic
2026-04-23 17:42 ` Simon Marchi [this message]
2026-04-27 10:26 ` [FYI] " Filipovic, Bratislav
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=ee9b6075-0b39-46b0-979b-fa45c535df3f@simark.ca \
--to=simark@simark.ca \
--cc=bfilipov@amd.com \
--cc=bratislav.filipovic@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=tdevries@suse.de \
/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