From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [committed][gdb/symtab] Fix incomplete CU list assert in .debug_names
Date: Fri, 22 May 2020 13:12:56 -0600 [thread overview]
Message-ID: <87wo534wcn.fsf@tromey.com> (raw)
In-Reply-To: <20200511130443.GA18365@delia> (Tom de Vries's message of "Mon, 11 May 2020 15:04:44 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> +set debug_names \
Tom> + [list \
Tom> + " .4byte .Ldebug_names_end - .Ldebug_names_start" \
Tom> + ".Ldebug_names_start:" \
Tom> + " .short 5 # Header: version" \
Tom> + " .short 0 # Header: padding" \
Tom> + " .long 1 # Header: compilation unit count" \
Tom> + " .long 0 # Header: local type unit count" \
Tom> + " .long 0 # Header: foreign type unit count" \
[...]
I think in the longer run it would be better to add real debug_names
support to the DWARF assembler than to keep doing this kind of thing.
Tom
prev parent reply other threads:[~2020-05-22 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:04 Tom de Vries
2020-05-22 19:12 ` Tom Tromey [this message]
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=87wo534wcn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--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