From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How does objdump sound in plan9?
Date: Tue, 11 Sep 2001 16:01:09 -0400 [thread overview]
Message-ID: <20010911200111.70F41199E9@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
> Well, acid takes care of a.out files, but what about .8s & Co? There seems
> no way to load an object file with unresolved references into acid or
> db to that matter.
Oh, that. Sorry, 'fraid I don't have a good answer to that one.
Plan 9 object files (as you may already be aware) are quite
different to those found on other platforms. They are
actually a form of binary assembly laguage which the
linker assembles.
What exactly are you trying to do? It sounds vaguely
interesting. You might want to try digging around
inside /sys/src/libmach
[-- Attachment #2: Type: message/rfc822, Size: 1852 bytes --]
From: Andrew Pochinsky <avp@honti.mit.edu>
To: 9fans@cse.psu.edu
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] How does objdump sound in plan9?
Date: Tue, 11 Sep 2001 15:46:25 -0400 (EDT)
Message-ID: <200109111946.f8BJkPS09447@honti.mit.edu>
Well, acid takes care of a.out files, but what about .8s & Co? There seems
no way to load an object file with unresolved references into acid or
db to that matter.
From: David Gordon Hogan <dhog@plan9.bell-labs.com>
Date: Tue, 11 Sep 2001 15:22:47 -0400
> Not quite. nm prints the name list, but I'm looking for groking the
> instructions.
man acid
next reply other threads:[~2001-09-11 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 20:01 David Gordon Hogan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 19:22 David Gordon Hogan
2001-09-11 19:34 ` Boyd Roberts
2001-09-11 19:46 ` Andrew Pochinsky
2001-09-11 18:47 Russ Cox
2001-09-11 18:54 ` Andrew Pochinsky
2001-09-11 18:42 Andrew Pochinsky
2001-09-11 19:04 ` Boyd Roberts
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=20010911200111.70F41199E9@mail.cse.psu.edu \
--to=dhog@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).