This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch] Unterminated .eh_frame when using --eh-frame-hdr

From: Ulrich Drepper <drepper at redhat dot com>
To: Richard Sandiford <rsandifo at redhat dot com>
Cc: libc-alpha at sources dot redhat dot com
Date: Mon, 08 Nov 2004 07:02:21 -0800
Subject: Re: [Patch] Unterminated .eh_frame when using --eh-frame-hdr
Organization: Red Hat, Inc.
References: <wvn1xf4za13.fsf@talisman.cambridge.redhat.com> <418F87FF.8020208@redhat.com> <wvnwtwwxucn.fsf@talisman.cambridge.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Sandiford wrote:

> But if the .eh_frame_hdr format says that the table is optional
> (and it does), shouldn't glibc be prepared to cope with that?

No, why should it?  We use them like this and it reduces the number of
things which can go wrong and which people have to be aware of when
changing the code.  Every new configuration option increases the
maintenance burden.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBj4p92ijCOnn/RHQRAjxXAJ98X4CAT5aKiD+9MuP28EU02FnMxACdFniH
H8dqt8yFHDrK281c5IyRVxc=
=75NX
-----END PGP SIGNATURE-----

References:
- [Patch] Unterminated .eh_frame when using --eh-frame-hdr
  - From: Richard Sandiford
- Re: [Patch] Unterminated .eh_frame when using --eh-frame-hdr
  - From: Ulrich Drepper
- Re: [Patch] Unterminated .eh_frame when using --eh-frame-hdr
  - From: Richard Sandiford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]