This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re[2]: Core dumps
- To: Christopher Faylor <cgf at cygnus dot com>, cygwin-developers <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re[2]: Core dumps
- From: Egor Duda <deo at logos-m dot ru>
- Date: Tue, 4 Jan 2000 16:57:34 +0300
- Organization: DEO
- References: <19991229161240.E7370@cygnus.com>
- Reply-To: Egor Duda <deo at logos-m dot ru>
Hi!
Dec 30 1999 Christopher Faylor <cgf@cygnus.com> wrote:
CF> This is great stuff. I've been meaning to ask you about this for
CF> some time.
CF> It is likely that this won't apply cleanly against gdb, at least, but
CF> we'll let you know.
I've looked at gdb and bfd snapshots from 1999-12-21, and remake all
patches. Seems that new StackWalk scheme won't work with core files
(at least i don't know if it is possible to use SymInitialize() & Co.
APIs without having running process, so i left old way of stack
tracing if we debug core dump. I've also changed winsup patch to
provide synchronization between core dumper and trapped process, and
to prevent recursive "error_start"ing of processes -- debugger can
possibly trap, and if so, we'll effectively get machine down with
a lots of spawning processes.
Patch to bfd includes configure.in changes, so 'configure' script
should be regenerated.
I've also encountered a small problem with gdb-19991221 -- it handles
global cygwin1.dll variables like 'myself' or 'tty_master'
incorrectly (_without my patches too_). I'll try to research this
problem if i have time.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
core_dump_patch.v2.tgz