Mail Archives: cygwin/2007/12/06/07:22:38
On Thu, Dec 06, 2007 at 12:44:38PM +0100, Corinna Vinschen wrote:
>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
>the distro:
>
>(gdb) i thr
> 3 process 1984 0x7c95077b in ntdll!KiIntSystemCall ()
> from /mnt/c/WINDOWS/system32/ntdll.dll
> 2 process 3020 0x7c90eb94 in ntdll!LdrAccessResource ()
> from /mnt/c/WINDOWS/system32/ntdll.dll
>* 1 process 3836 0x7c90eb94 in ntdll!LdrAccessResource ()
> from /mnt/c/WINDOWS/system32/ntdll.dll
>
>None of the backtraces shows anything beyond the system DLLs.
>
>Do we also need a newer GDB for this to be useful?
I'm not aware of any advances in frame handling in the CVS version of gdb
but I'm waiting for the recent spate of win32 activity to die down before
I release a new version of gdb.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -