Forum > General
FPC 3.2.2 - Debug Information's are always present
paule32:
Hi,
I used the command line tool FPC with option: -g-
I read, that this option will turn off the generating of debug information's - but when I look to the created assembly, the debug symbols and a bunch of code in SECTION .debug_frame can be found.
Is there no way to force it out ?
TRon:
have you tried icw -Xs and if that isn't enough using strip binutil manually ?
paule32:
yes, I tried:
--- Code: Bash [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---ppcrossx64.exe -Xs -Fu..\sources\fpc-sys -Anasmwin64 -a -g- test.pas
but the debug_frame SECTION is still present.
I know strip.exe.
But I was thinking, that the DEBUG stage contains extra binary code in the image...
MarkMLl:
Roughly translated: you'd expect to see debug info in the assembly output since whether it's in the binary or not is determined by the linker. In extremis, you can use the strip command (part of binutils) to remove debug info from the final binary, although as you'll see from a recent thread (and I'm sure you did a bit of research before posting) that doesn't remove RTTI.
MarkMLl
TRon:
Indeed MarkMLI.
In the other thread paule32 was using objdump so was expecting that and not the assembler output created by the compiler. My bad.
Navigation
[0] Message Index
[#] Next page