It looks working, if i switch to Dwarf2 instead of Dwarf with sets.Not yet heard of this one.
There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.
There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.This also is in latest trunk. Very aanoying :(
One question more, what did automatic do :-) ?
There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.This also is in latest trunk. Very aanoying :(
Afaik it does not depend on the Lazarus version, but on the version of fpc. But not sure. (Older Lazarus, came with older FPC)
And with 64bit breakpoints are only transmitted to the debugger while program is paused (F12).
There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.
This also is in latest trunk. Very aanoying :(
\FPC\SVN-build\install\crossbinw64\x86_64-win64-objcopy.exe -R .debug_frame project1.exe project1n.exe
If you do it right, it shrinks by just a few MB (an empty form1 goes from 27MB to 26MB)Off topic from the original post.
Related only to the following issue reported later in this thread:There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.
This also is in latest trunk. Very annoying :(
Try the following.
You need an "objcopy" for win 64 bit apps. The only one I could find is in the fpc-build repository, with the tools for cross compiling to 64 bits (but it works fine).
The one that comes with fpc 32 bit, will not work.Code: [Select]\FPC\SVN-build\install\crossbinw64\x86_64-win64-objcopy.exe -R .debug_frame project1.exe project1n.exe
If you do it right, it shrinks by just a few MB (an empty form1 goes from 27MB to 26MB)
then copy project1n.exe back to the original, or set "run parameters" to use the new one.
It may be possible to add this to project opitons "compiler commands"
<-data-evaluate-expression $fp>F8 in Debuggerwindow
^done,value="0x195f8d8"
(gdb)
<-exec-step>
^error,msg="Warning:\nCannot insert breakpoint -233.\nCannot access memory at address 0x72d54ef4\n"
(gdb)
<-break-enable 10>Comandlineparameters (from Projectoptions - Show Options) without the -F !
^done
(gdb)
<-break-enable 9>
^done
(gdb)
<-data-evaluate-expression $fp>
^done,value="0x195f8d8"
(gdb)
<-exec-next>
^error,msg="Warning:\nCannot insert breakpoint -236.\nCannot access memory at address 0x72d54ef4\n"
(gdb)
-MObjFPC -Scaghi -CirotR -O1 -g -gl -gh -Xg -gt -WG -l -vewnhibq
^error,msg="Warning:\nCannot insert breakpoint -233.\nCannot access memory at address 0x72d54ef4\n"
Yes! Works great. I found a newer one here https://svn.freepascal.org/svn/fpcbuild/binaries/i386-win32 (https://svn.freepascal.org/svn/fpcbuild/binaries/i386-win32)
Many thanks, Martin!
Yes! Works great. I found a newer one here https://svn.freepascal.org/svn/fpcbuild/binaries/i386-win32 (https://svn.freepascal.org/svn/fpcbuild/binaries/i386-win32)
Many thanks, Martin!
Well, after using this the whole day, i must say that i have problems with F7 now %)
Sometimes it works like F9 and sometime the IDE says the program is running while it isn't reacting anymore.
There is an issue with 64bit (possible only if fpc 3.0.4 is used, not sure) where step over, will step in.
This also is in latest trunk. Very aanoying :(