Re: TLS-version of libc6/{testing,unstable} breaks libunwind
References: <200408191136.i7JBaxZb026752@napali.hpl.hp.com>
<811xi2ii1k.wl@omega.webmasters.gr.jp>
<16677.42925.379194.878994@napali.hpl.hp.com>
<81oekereqn.wl@omega.webmasters.gr.jp>
<16759.35734.564337.953191@napali.hpl.hp.com>
<816553y0gh.wl@omega.webmasters.gr.jp>
<16760.46697.989684.514746@napali.hpl.hp.com>
<81pt34w0af.wl@omega.webmasters.gr.jp>
<16768.50197.648342.935088@napali.hpl.hp.com>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigory?òmae) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
Fcc: %Mail/mbx/Backup
--text follows this line--
At Thu, 28 Oct 2004 03:04:05 -0700,
David Mosberger wrote:
> >>>>> On Thu, 28 Oct 2004 02:14:48 +0900, GOTO Masanori <gotom@debian.or.jp> said:
>
> GOTO> We got security bug report; it may be chance to switch -19.
>
> Cool. I suddenly like security bugs... ;-)
Yeah, it's another side effects :)
> GOTO> I put no -fomit-frame-pointer .deb based on -18 at:
> GOTO> http://www.gotom.jp/~gotom/debian/glibc/2.3.2.ds1-18_i386.fofp/
>
> OK, I tried this on an x86 laptop and it does indeed fix the libunwind
> failures that were due to -fomit-frame-pointer/lack-of-unwind-info.
Thanks for your checking and your detailed comment as usual, I've put
the patch :)
At Sat, 30 Oct 2004 21:56:26 -0400,
Daniel Jacobowitz wrote:
> Go ahead, I guess.
>
> We should really talk about just turning on unwind tables instead by
> default, and see what the size impact is. Later.
Thanks ack. And ok - we'll need to consider about unwind tables.
Regards,
-- gotom
Reply to: