This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.5.24-2: unalbe to get a core Dump file
On Dec 6 12:01, Corinna Vinschen wrote:
> On Dec 5 23:13, Pedro Alves wrote:
> > Brian Dessent wrote:
> >> As already mentioned downthread, if you want a core dump you should
> >> simply set error_start=c:/cygwin/bin/dumper.exe, modulo dumper bugs
> >> (which should have all been fixed in the latest version.)
> > The cvs version still doesn't work for me if I link
> > it with the distributed bfd -- it crashes in that case.
> > The latest fixes were done with a bfd from cvs.
> > I haven't tried the latest test version, but
> > should have the same problem.
> Do you imply that we need a new binutils package to get dumper working?
I just built dumper with a bfd from CVS HEAD(*). It seems to work on
the first glance. Setting error_start as above, it catches the division
by zero from the OP's test app and creates a core file. However, this
core file doesn't seem to be very helpful, at least when using GDB from
(gdb) i thr
3 process 1984 0x7c95077b in ntdll!KiIntSystemCall ()
2 process 3020 0x7c90eb94 in ntdll!LdrAccessResource ()
* 1 process 3836 0x7c90eb94 in ntdll!LdrAccessResource ()
None of the backtraces shows anything beyond the system DLLs.
Do we also need a newer GDB for this to be useful?
(*) Btw., the new testrelease 1.5.24-4 contains this dumper.exe
linked against bfd from CVS HEAD.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html