public inbox for
 help / color / mirror / Atom feed
From: ASSI <>
Subject: Re: Replacement for "objdump -d -l"?
Date: Thu, 17 Aug 2023 20:38:59 +0200	[thread overview]
Message-ID: <87wmxtbjjw.fsf@Rainer.invalid> (raw)
In-Reply-To: <> (Nick Clifton via Binutils's message of "Tue, 15 Aug 2023 15:15:01 +0100")

Nick Clifton via Binutils writes:
> But to be fair, the output format does not change that much, and
> it could be documented if there really was a need.

I've implemented a Perl script that just extracts the file and directory
tables from the -WNl dump and checks which of these actually get
referenced by line number statements.  The latter part is necessary
since there are more files in the tables than are actually used in line
number statements.  I still extract more files than what I am getting
from "objdump -dl", these extras seem to be instances where the same
address in the disassembly has multiple views associated (not analysed,
but from the files involved these might be resulting from macro
expansions).  I have not yet figured out which of these views is the one
that ends up in the disassembly with line numbers dump, but for the
prupose of debugging it seems I should actually keep debug sources for
all views the debugger might encounter.  The other snag I've hit is
relative directories in the directory table, but with the examples I've
seen so far these resolve relative to directory entry #0 (which is
otherwise unreferenced by file table entries).

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:

  reply	other threads:[~2023-08-17 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 18:35 ASSI
2023-08-15 14:15 ` Nick Clifton
2023-08-17 18:38   ` ASSI [this message]
2023-08-22 12:17   ` Richard Earnshaw (lists)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmxtbjjw.fsf@Rainer.invalid \ \ \

* 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).