- Settings are all ok
- Also happens with 2.6.2 on 32 bit, GDB 7.2.1
- Works (but not as you would expect) with 32 bit gdb 7.5.1 (But see notes below)
\nCannot insert breakpoint 8.\nError accessing memory address 0x3d: Input/output error.
For some reason the address is not relocated when the program is loaded.
I made 2 observations:
*** 1)
GDB 7.2.1 does show "line info" (blue dots) on that line. Indicating that the code is used.
GDB 7.5 does indicate this code is not used (never called) (So it gives no error, but the breakpoint will not be there either)
If the code is not used, and possible not linked into the exe, then those relocation errors do happen. IIRC there is a bug, that line info for none used code is included, even if the code is not.
Seems that older GDB fails with that.
*** 2)
I also noted, that if I rename the file, all works fine.
So I guess that the original file with the same name is still partly used, and some methods in the exe are taken from the original file.
-----------------------------------------------
I do not know what you try to do: but simply creating a file with the same name as in the fpc package, will not redirect all calls into your version.
Only calls that are made in your units (including the ones with the copied name).
You also use "fpimage" but from the original fpc location. Any call this makes to fpreadtiff, may (not sure if all, but at least some) still go to the original file.
Besides that: this kind of double file names can lead to lots of troubles.