This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: Help: Unwinding the C++ stack...throw, longjmp & threads
- To: mark@codesourcery.com (Mark Mitchell)
- Subject: Re: Help: Unwinding the C++ stack...throw, longjmp & threads
- From: Joern Rennecke <amylaar@cygnus.co.uk>
- Date: Wed, 25 Aug 1999 06:44:31 +0100 (BST)
- Cc: jbuck@synopsys.COM, jason@cygnus.com, drepper@cygnus.com, george@moberg.com, kriol@fnal.gov, gcc@gcc.gnu.org, libc-alpha@sourceware.cygnus.com
> There may be systems on which glibc is used, but statically linked.
> There, I would see more of an issue, as every binary would grow. (For
> example, this might be true if glibc were ported to a system without
> shared library support in binutils.) But, I think we should cross
> that bridge when we come to it.
This could be solved by stripping the exception information if a program is
linked wherenoneof the non-library object files have exception information.
Then anordinary C program should get nosize increase.