This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Designs for better debug info in GCC. Choice A or B?
To imagine that i'm using "-g -Os -finline-functions -funroll-loops".
There are differences in how to generate "optimized AND debugged" code.
A) Whole-optimized but with dirty debugged information if possible.
------------------------------------------------------------------------------------
When there is coredump from crash then its debugged information can
be not complete (with losses) but can be readable for humans.
This kind of strategy can't work well in "step to step" debuggers like
gdb, ddd, kgdb, ... but its code is whole-optimized same as stripped program.
B) Whole-debugged but partially optimized because of restricted requirements
to maintain the full debugged information without losses.
------------------------------------------------------------------------------------
This kind of strategy works well in "step to step" debuggers like
gdb, ddd, kgdb, ... but its code is less whole-optimized and bigger than
stripped program.
Sincerely, J.C.Pizarro