Windows 7 64bit and gdb

[Bernd]

Look here: http://bugs.freepascal.org/view.php?id=15692

You can use the "-WB" compiler switch or use a include file {$I ...} which contains {$IMAGEBASE ...) and is included into every unit. Whatever you prefer.

[Marc]

OK, i did some tests with the 64bit gdb 7.0.50 debugger and I could debug when I enable dwarf debug info (-gw) for the project options (linker)
Without it it seems that dwarf info is generated (at least that is what "maintenance info symtabs" shows)
So no change of imagebase needed.

[jscrump]

I am having trouble with debugging in Vista 64 with Lazarus 0.9.29 SVN 24843, FPC 2.4.1.

I've tried the newest gdb 7.1.50.20100411-cvs and adding -WB00400000 to other compiler options.

I have all of the checks enabled under "Code", level 1 for "Optimizations". Under linking I have selected: Generate debugging info for GDB, Display line numbers for Run-time ...., Use external gdb debug symbols file. And Win32 gui application.

The debug output looks fine until:
(gdb)
&"Warning:\n"
&"Cannot insert breakpoint 1.\n"
&"Error accessing memory address 0x2aa0: Input/output error.\n"
&"Cannot insert breakpoint 97.\n"
&"Error accessing memory address 0x10002aa0: Input/output error.\n"
&"Cannot insert breakpoint 122.\n"
&"Error accessing memory address 0x2af0: Input/output error.\n"
&"\n"
^error,msg="Warning:\nCannot insert breakpoint 1.\nError accessing memory address 0x2aa0: Input/output error.\nCannot insert breakpoint 97.\nError accessing memory address 0x10002aa0: Input/output error.\nCannot insert breakpoint 122.\nError accessing memory address 0x2af0: Input/output error.\n"
(gdb)
<info program>
&"info program\n"
~"\tUsing the running image of child thread 3488.0xf30.\n"
~"Program stopped at 0x0.\n"
~"Type \"info stack\" or \"info registers\" for more information.\n"
^done

I can start the new gdb in a command prompt and run the program fine, but I can debug it.

Does any one have any ideas on what I am missing or doing wrong?

Thanks
Jeff Crump