Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Mon, 10 May 1999 20:48:38 +0400
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.029) S/N A0F2A05A
Reply-To: Egor Duda <deo AT logos-m DOT ru>
Organization: DEO
Message-ID: <13867.990510@logos-m.ru>
To: cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
CC: Chris Faylor <cgf AT cygnus DOT com>
Subject: new core files
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

May 8 1999, Chris Faylor <cgf AT cygnus DOT com> wrote:

 CF> I should point out that the subject of core dumps was recently raised
 CF> in some gdb discusions.  There seems to be a general consensus that
 CF> for targets, like cygwin, which don't support a native core dump
 CF> format, that the target should use the ELF core dump format.  It seems
 CF> to be the most flexible format for this type of thing.

I've  tried  to  do it using bfd. It works ok, i've only needed to add
new  note  section type to store CONTEXT structure and function to bfd
code  to  pass it to gdb. But it makes cygwin (not cygwin1.dll itself,
but "core-dumper" tool) dependent on bfd. is it ok?

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19