delorie.com/archives/browse.cgi | search |
Date: | Sat, 31 Mar 2001 04:43:49 -0500 (EST) |
Message-Id: | <200103310943.EAA16316@indy.delorie.com> |
From: | Eli Zaretskii <eliz AT delorie DOT com> |
To: | jtc AT redback DOT com |
CC: | taylor AT cygnus DOT com, gdb AT sources DOT redhat DOT com, sandmann AT clio DOT rice DOT edu, |
djgpp-workers AT delorie DOT com | |
In-reply-to: | <5m3dbvca9s.fsf@jtc.redback.com> |
Subject: | Re: Adding support for core files to DJGPP |
References: | <200103301443 DOT JAA24895 AT texas DOT cygnus DOT com> |
<200103301534 DOT KAA28533 AT indy DOT delorie DOT com> <5m3dbvca9s DOT fsf AT jtc DOT redback DOT com> | |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: jtc AT redback DOT com (J.T. Conklin) > Date: 30 Mar 2001 11:43:59 -0800 > > 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. Is there any place one can see the code or docs of what you've written?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |