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: <3FE0A59A.6060802@kaffe.org>
Date: Wed, 17 Dec 2003 19:51:06 +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: Need tips debugging a crash porting an app to cygwin caused by sth overwriting a function
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by AMaViS perl-11
X-IsSubscribed: yes

Hi all,

I'm trying to get kaffe to work again on Cygwin, and I'm quite puzzled 
at a bug I'm seing. Here's what happens:

I fire up a statically linked kaffe-bin.exe in gdb, and disassemble a 
function, findJarFiles in gdb, and result looks reasonable, i.e. it 
looks just like in the disassembly of the object file the function comes 
from.

I try runing kaffe in gdb in order to run the java compiler, and quite 
quickly, it crashes, when it enters the findJarFiles function, with a 
SIGSEGV. The disassembly of the function shows that it's been modified 
to have a few bad opcodes at the start.

Of course, I'd like to know what causes those opcodes to be modified. 
I've tried watch and awatch findJarFiles, awatch *(long *) findJarFiles, 
but despite gdb saying that it's setting a hardware watchpoint, I don't 
get a break in gdb until the function call crashes, which is too late.

So I'm wondering what kind of tips experienced Cygwin developers could 
offer to nail the bug down.

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/