From: jtc@redback.com (J.T. Conklin)
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: taylor@cygnus.com, 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 11:44:00 -0000 [thread overview]
Message-ID: <5m3dbvca9s.fsf@jtc.redback.com> (raw)
In-Reply-To: <200103301534.KAA28533@indy.delorie.com>
>>>>> "Eli" == Eli Zaretskii <eliz@delorie.com> writes:
>> Date: Fri, 30 Mar 2001 09:43:39 -0500
>> From: David Taylor <taylor@cygnus.com>
>>
>> If you are designing the core file format for DJGPP, I would recommend
>> making it an ELF file.
Eli> It sounds like that: you are the second person (out of two who
Eli> replied) who suggested that. Thanks.
For a host environment like DJGPP, I agree with the recommendation for
ELF crash dumps.
However, I wanted to mention that for embedded environments, it may be
better to use a custom crash dump format. One requirement I had was I
had to write dumps to streaming media (in other words, no seeks). I
suspect I could have written ELF dumps by doing two passes over the
system (one to compute the offsets, another to write the dump), it was
simpler to use a format designed for streaming from the get go.
--jtc
--
J.T. Conklin
RedBack Networks
next prev parent reply other threads:[~2001-03-30 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 6:44 David Taylor
2001-03-30 7:49 ` Eli Zaretskii
2001-03-30 11:44 ` J.T. Conklin [this message]
2001-03-31 1:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2001-03-30 9:34 David Taylor
2001-03-30 11:14 ` H . J . Lu
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=5m3dbvca9s.fsf@jtc.redback.com \
--to=jtc@redback.com \
--cc=djgpp-workers@delorie.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=sandmann@clio.rice.edu \
--cc=taylor@cygnus.com \
/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