X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 6 Dec 2007 13:55:54 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.5.24-2: unalbe to get a core Dump file Message-ID: <20071206125554.GQ26345@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47568201.80303@garr.it> <4756E558.1A70439F@dessent.net> <47573096.7050007@portugalmail.pt> <20071206110146.GL26345@calimero.vinschen.de> <20071206114438.GN26345@calimero.vinschen.de> <20071206122212.GA6144@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071206122212.GA6144@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Dec 6 07:22, Christopher Faylor wrote: > 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. That makes sense. A new binutils package might be helpful, though. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/