[fpc-devel] gdb on amd64

Marco van de Voort marcov at stack.nl
Wed Jun 1 22:43:43 CEST 2005

> I am investigating a crash of lazarus on the amd64 platfrom.
> Part of the backtrace looks like this:
> #18 0x0000000000434ea0 in TAPPLICATION__RUN (this=Cannot access memory 
> at address 0x8000ffffed18
> ) at application.inc:980
> Note the parameter of TApplication.Run is not shown, because of the 
> invalid memory address. Is this normal (can't gdb handle this?) or does 
> this indicate a bug in my program?

Sounds like calling a method of an object that isn't properly initialised or is corrupted.

More information about the fpc-devel mailing list