On Tue, Sep 23, 2003 at 12:23:27PM +0100, Philip Blundell wrote: > > Might it be an idea to kick this one upstream? > > Possibly, though I'm not sure which upstream. Since it's blowing up > during unwinding, that would suggest that either the unwind tables are > damaged, or the unwinder itself is buggy. In the former case it would > probably be a binutils bug; in the latter case it would probably be a > gcc bug. I think some further investigation is needed.
(has nothing to do with nptl) Ok, i could further track it down: as stated before: works: * this is glibc as of 2003-07-02T11:06:49-0700 and nptl 0.52 I recompiled with sid -> segfault I changed to old compiler -> segfault I changed to binutils_2.14.90.0.4-0.1 -> works I changed to binutils_2.14.90.0.5-0.1 -> segfault So it's a binutils bug, I think. Christian Leber -- "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." (Aurelius Augustinus) Translation: <http://gnuhh.org/work/fsf-europe/augustinus.html> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
