Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3FE341DF.90800@kaffe.org>
Date:	Fri, 19 Dec 2003 19:22:23 +0100
From:	Dalibor Topic <robilad AT kaffe DOT org>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Setting breakpoints before main
X-Virus-Scanned:	by AMaViS perl-11
X-IsSubscribed:	yes

Hi all,

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.

The opcode at the start of the function in question is apparently 
modified before the program actually calls main. So when I break on main 
in gdb, and print the value of the first opcode of the function before I 
run the program, and after it breaks at main, the first opcode of the 
function in question is different, which leads to a crash as soon as the 
function is called.

Since I'd like to know what modifes that opcode, I hope to be able to 
set a breakpoint in gdb on the code that is executed before main in Cygwin.

Any idea how to do that, i.e. where to put the breakpoint? Are there 
some docs on what happends before main() on cygwin that I could look up 
for reference while trying to hunt down this bug?

cheers,
dalibor topic


--
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 -