my vote would be to have just one generic flag gdb info is misleading since dwarf can be used by many tools including lldb  and libbacktrace i like debugsymbols more i would say it sounds like a dwarfsymbols  i e debug sections but not everyone might not know the name dwarf so it is good generic name but both of the above seem to imply that they only control inclusion exclusion of debug data i think it would be conceivable that the flag could have deeper effects say  do not deduplicate methods to make sure they can be identified  or omit some optimizations that rearrange code anyway  this is just bike shedding about names i would not want to change it as part of this cl i picked gdbinformation here somewhat randomly  and made sure it is at least consistent with quick and elf writer should i change it back to getincludedebugsymbols and maybe kill gdb in further cl  