Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: Ralf Habacker To: Dalibor Topic , Steve Coleman Subject: Re: How to set breakpoints before mainCRTStartup? Date: Tue, 23 Dec 2003 19:07:20 +0100 User-Agent: KMail/1.5.4 Cc: cygwin AT cygwin DOT com References: <3FE341DF DOT 90800 AT kaffe DOT org> <3FE70A9A DOT 6070005 AT jhuapl DOT edu> <3FE87A1C DOT 1020405 AT kaffe DOT org> In-Reply-To: <3FE87A1C.1020405@kaffe.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312231907.20249.ralf.habacker@freenet.de> X-IsSubscribed: yes On Tuesday 23 December 2003 18:23, Dalibor Topic wrote: > >>> in my attempts to fix an ugly bug in kaffe on Cygwin, the bug I'm > >>> trying to squish turned out to be triggered by something that happens > >>> *before* main is called. > > you can set a breakpoint at the application entry point. $ gdb /bin/bash (gdb) info file Symbols from "/usr/bin/bash.exe". Local exec file: `/usr/bin/bash.exe', file type pei-i386. Entry point: 0x401000 0x00401000 - 0x0047b754 is .text 0x0047c000 - 0x00480d90 is .data 0x00481000 - 0x00488f60 is .bss 0x00489000 - 0x0048a12c is .idata (gdb) b *0x401000 Breakpoint 1 at 0x401000 (gdb) r Starting program: /usr/bin/bash.exe Breakpoint 1, 0x00401000 in ?? () (gdb) Ralf -- 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/