Message-Id:	<4.2.0.58.19991124161000.00a11cb0@hal.nt.tuwien.ac.at>
X-Sender:	tony AT dictator DOT nt DOT tuwien DOT ac DOT at
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date:	Wed, 24 Nov 1999 16:25:47 +0100
To:	djgpp AT delorie DOT com
From:	Anton Helm <tony AT dictator DOT nt DOT tuwien DOT ac DOT at>
Subject:	Re: Problems with DJGPP lib and grx23
In-Reply-To:	<199911241200.NAA05607@acp3bf.physik.rwth-aachen.de>
Mime-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

At 01:00 PM 11/24/99 +0100, you wrote:

 >You (or someone) will have to dig a bit deeper: generate the crash
 >inside a gdb session or write down the exact address found in the
 >coredump (i.e. traceback). Then *disassemble* the above routine, and
 >find out what instruction is causing the problems.  Print register
 >contents. Try to deduce what's happening.

Main problem with debugging is that this is a graphic application
and the problem is related to displaying a mouse cursor.
I am no gdb guru either but to my experience it isn't that easy to
debug such programs with gdb. (At least I always managed to avoid it.)

I've stopped graphic programming years ago. All my newer programs
are text interface oriented and most of them commandline only.
Life's much easier that way. 
My current problem is that someone requested a new feature in a 6 year
old program. The new feature itself wasn't that complicated but
it took a day to get the whole thing running because of that library 
problem.

BTW: I was impressed that this graphic application also works
with WinNT 4.0 now.

Tony

- Raw text -