This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: PATCH to mklibgcc.in for EH debugging
>>>>> "Jakub" == Jakub Jelinek <jakub@redhat.com> writes:
> On Fri, Mar 15, 2002 at 11:18:03AM -0500, DJ Delorie wrote:
>>
>> > Do people think hardcoding this here is OK, or should I make it a new
>> > variable in the Makefile.in?
>>
>> Most people would not benefit from such debug information, and it
>> would increase the size of the installed libgcc.a. Perhaps it could
>> be triggered off maintainer mode? I too like -g2 for libgcc.a (all of
>> it, not just exception code).
I would think that anyone who wants to debug a program that uses EH would
benefit from it; gdb isn't yet clever enough to handle stepping past a
throw to the catch clause. Of course, they'd need to have the appropriate
sources around...
Sometimes I have to debug a program built by someone else; if their libgcc
installation doesn't have debug info, that can be hard. It's the usual
rationale for building GNU software with debug info by default. If you
don't want it, there's always strip.
I've never had a need to debug anything else in libgcc, but YMMV.
And I don't turn on maintainer mode, as it has a tendency to try and fail
to rebuild the boehm-gc makefiles. :)
> Or enabled if checking is enabled and disabled with --disable-checking?
They seem like orthogonal issues to me.
Jason