From: Ian Lance Taylor <ian@zembu.com>
To: scottb@netwinder.org
Cc: binutils@sourceware.cygnus.com
Subject: Re: Patch to readelf...
Date: Thu, 19 Aug 1999 12:40:00 -0000 [thread overview]
Message-ID: <19990819194018.802.qmail@daffy.airs.com> (raw)
In-Reply-To: <37BC3E3B.F1F54264@netwinder.org>
Date: Thu, 19 Aug 1999 13:26:19 -0400
From: scottb <scottb@netwinder.org>
If I remove the arm_* functions, is the remaining code still too Linux
specific? I'm not familiar enough with other architechures to know if
the information in the notes is common enough for general use.
If people think it is worth pursuing, I'll happily tidy up the patch for
further review.
I think it would be nice if readelf could dump information from core
files.
Ideally it would be done in a manner which would work when cross
compiling. That means that you can not use header files like
<sys/procfs.h> which are not present on every system. It means that
you must define the structures yourself. It means that you must swap
the data in case the host and target have a different endianness.
In practice, of course, core files are not that common when
cross-compiling. Therefore, I think it would be acceptable to only
support core file dumping on a native system. This means configury
work to only compile code on the appropriate system.
Ian
next prev parent reply other threads:[~1999-08-19 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-19 9:29 Nick Clifton
1999-08-19 9:47 ` Jakub Jelinek
1999-08-19 11:56 ` scottb
1999-08-19 12:40 ` Ian Lance Taylor [this message]
1999-08-30 12:11 ` scottb
-- strict thread matches above, loose matches on Subject: below --
1999-08-31 10:00 Nick Clifton
1999-08-31 1:47 Nick Clifton
1999-08-31 8:40 ` scottb
1999-08-19 8:10 scottb
1999-08-19 11:24 ` Ian Lance Taylor
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=19990819194018.802.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=scottb@netwinder.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 read-only IMAP folder(s) and NNTP newsgroup(s).