You are of course correct that it does not preclude it. On certain systems I too have happily debugged optimized code. On my present system (gdb 7.6.1, gcc 4.9.3, msys/mingw32, Windows Server 2008 R2) I must say debugging -O2 optimized code is definitely inconvenient, often tiresome, sometimes impossible.
GNUstep Makefile Package documentation [1] says if debug=yes, optimization is off. (It further says that the user must override the optimization flag if both debugging information and optimization are desired.) Note that OPTFLAG := $(filter-out -O%, $(OPTFLAG)) clearly intends to do so but fails because the optimization flag already entered ADDITIONAL_FLAGS (hence the suggested patch). Ref: [1] “make debug=yes” at http://www.gnustep.org/resources/documentation/make_1.html <http://www.gnustep.org/resources/documentation/make_1.html>
_______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
