Re: [fpc-devel] gdb on amd64
I am investigating a crash of lazarus on the amd64 platfrom. Part of the backtrace looks like this: #18 0x00434ea0 in TAPPLICATION__RUN (this=Cannot access memory at address 0x8000ed18 ) 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. It is a 32bit - 64bit conversion error. gdb converts a signed 32bit to as an unsigned 32bit to 64bit. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] gdb on amd64
Hi, I am investigating a crash of lazarus on the amd64 platfrom. Part of the backtrace looks like this: #18 0x00434ea0 in TAPPLICATION__RUN (this=Cannot access memory at address 0x8000ed18 ) 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? Regards, Vincent. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
