Thanks Keith I am thinking of a silly way to check it: create with and without -g, then compare sizes, and even use 'diff' if same.
Not guaranteed to be a comprehensive check, but gives a clue anyway. Michael -----Original Message----- From: Keith Rollin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 5 December 2001 3:22 PM To: Palm Developer Forum Subject: Re: Is .prc affected by -g flag ? BTW: I checked the build-prc sources. They read in the .text, .data, .bss, and .reloc sections. I don't see them read in .debug sections. But I only checked the process_binary_file() function in binres.cpp. -- Keith At 7:50 PM -0800 12/4/01, Keith Rollin wrote: >I think that most people use -g for debug versions, and something >like -O2 for release versions. But if you want to use the same >options (-g) for both, I think that's OK. I don't think that any >symbolic debugging information makes it into the .prc file. > >-- Keith "that's just a guess until John Marshall corrects me, or > until somebody decides to read the part of the documentation > that probably exists on this topic" > >>For GCC you normally put -g flag to enable debugging. >> >>This produceses some extra staff (presumably NOP commands with line numbers) >>in COFF. >>But will .prc file be affected ? >> >>In other words, should I recompile the whole application with out -g, >>(add m68k-palmos-strip, etc) for the release, or leave it as it is ? >> >>Regs >>Michael -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
