This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: S/390: Default to -fasynchronous-unwind-tables
- From: "Ulrich Weigand" <Ulrich dot Weigand at de dot ibm dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Richard Henderson <rth at redhat dot com>, gcc-patches at gcc dot gnu dot org, "Gerhard Tonn" <TON at de dot ibm dot com>
- Date: Thu, 21 Nov 2002 18:09:46 +0100
- Subject: Re: S/390: Default to -fasynchronous-unwind-tables
- Sensitivity:
Jakub Jelinek wrote:
>But without .symtab/.strtab the backtraces aren't much useful anyway.
>Which is not much different from making sure .debug_frame stays.
Not really. Even without symbolic names, a backtrace is still useful.
Also, you can build those parts you are interested in with debug info,
so a backtrace will show *those* symbols at least, even if you actually
crash in a system library.
But without backtrace, you can basically do nothing.
>> While you could certainly say that they should just build the app
>> with -g1, this doesn't help if the crash happens in a library routine.
>> One solution would be to build all system libraries also with -g1,
>> which we had considered, but this has the disadvantage that 'strip'
>> removes the information (and the usual RPM build process strips all
>> binaries and libraries) ...
>
>This is changing.
Well, that would also be an option. But I don't quite see why this
would be an improvement over using -fasynchronous-unwind-tables,
seeing as -g1 takes significantly more space, and additionally duplicates
.eh_frame info where that is needed anyway ...
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com