Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Taylor <taylor@cygnus.com>
To: Eli Zaretskii <eliz@delorie.com>
Cc: gdb@sources.redhat.com, sandmann@clio.rice.edu,
	djgpp-workers@delorie.com
Subject: Re: Adding support for core files to DJGPP
Date: Fri, 30 Mar 2001 09:34:00 -0000	[thread overview]
Message-ID: <200103301734.MAA24916@texas.cygnus.com> (raw)

    Date: Fri, 30 Mar 2001 10:34:29 -0500 (EST)
    From: Eli Zaretskii <eliz@delorie.com>

    > Date: Fri, 30 Mar 2001 09:43:39 -0500
    > From: David Taylor <taylor@cygnus.com>

    > I believe that the Sys V ABI specifies for Sys
    > V systems much of the core file layout stuff; rather than invent a new
    > format, I would suggest using that.

    Where can I find these specifications that you mention above?

Once upon a time, AT&T published (in conjuction with Prentice-Hall) a
set of books that describe the standard.  Titles like "System V
Application Binary Interface", "System V Application Binary Interface:
SPARC Processor Supplement", and "Understanding ELF Object Files and
Debugging Tools".  If you want to go the book route, I'd suggest
trying any good technical bookstore.

Some of this information is available on the web.  I know that some of
the Unix API stuff is available on the web site for the "The Open
Group"; I don't know whether the core file and ELF file ABI stuff is
available there or not, though.

You might also try SCO.


             reply	other threads:[~2001-03-30  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30  9:34 David Taylor [this message]
2001-03-30 11:14 ` H . J . Lu
  -- strict thread matches above, loose matches on Subject: below --
2001-03-30  6:44 David Taylor
2001-03-30  7:49 ` Eli Zaretskii
2001-03-30 11:44   ` J.T. Conklin
2001-03-31  1:43     ` Eli Zaretskii
2001-03-30  1:10 Eli Zaretskii
2001-03-30  2:32 ` egor duda
2001-03-30  3:28   ` Eli Zaretskii
2001-04-02  1:19   ` Eli Zaretskii
2001-04-02  3:20     ` egor duda

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=200103301734.MAA24916@texas.cygnus.com \
    --to=taylor@cygnus.com \
    --cc=djgpp-workers@delorie.com \
    --cc=eliz@delorie.com \
    --cc=gdb@sources.redhat.com \
    --cc=sandmann@clio.rice.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