From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu, pip@namaste.stricca.org
Subject: Re: [9fans] software ports
Date: Sat, 22 Jul 2000 11:36:50 -0400 [thread overview]
Message-ID: <200007221537.LAA00818@cse.psu.edu> (raw)
William Josephson and I have been discussing it, but
haven't done anything. Generating the raw ELF binaries
should be easy, but I haven't found any documents
that say what the debugging info -- the symbol/pc table
and the pc/source line table, not to mention the actual
variables -- looks like.
Without that, I'm sure we'll just hit a debugging wall.
Anyone know what gdb expects?
Russ
next reply other threads:[~2000-07-22 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-22 15:36 Russ Cox [this message]
2000-07-22 17:33 ` Mike Haertel
2000-07-25 8:41 ` Michael Joosten
-- strict thread matches above, loose matches on Subject: below --
2000-07-22 19:19 pip
2000-07-22 18:56 forsyth
2000-07-15 20:56 Russ Cox
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=200007221537.LAA00818@cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=pip@namaste.stricca.org \
/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).