On Wed, Dec 17, 2003 at 07:51:06PM +0100, Dalibor Topic wrote:
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.
Use 'display' to show the contents of the memory location being modified
and either single step or use binary search techniques to see when the
location is modified.
This isn't a cygwin technique. It's just a debugging technique.