X-Authentication-Warning: jtc.redback.com: jtc set sender to jtc AT redback DOT com using -f Sender: jtc AT redback DOT com To: Eli Zaretskii 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 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> From: jtc AT redback DOT com (J.T. Conklin) Date: 30 Mar 2001 11:43:59 -0800 In-Reply-To: <200103301534.KAA28533@indy.delorie.com> Message-ID: <5m3dbvca9s.fsf@jtc.redback.com> Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Precedence: bulk >>>>> "Eli" == Eli Zaretskii writes: >> Date: Fri, 30 Mar 2001 09:43:39 -0500 >> From: David Taylor >> >> 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