On Wed, Aug 31, 2011 at 07:26:10AM +0200, Mike Hommey wrote: > On Wed, Aug 31, 2011 at 07:05:04AM +0200, Mike Hommey wrote: > > On Wed, Aug 31, 2011 at 06:35:09AM +0200, Mike Hommey wrote: > > > Interestingly, according to bug #639851, 6.0-2 didn't have the problem. > > > Which suggests something else broke. > > > > Actually, it must have worked by luck in 6.0-2 for that user, because > > the binary is affected the same way. > > > > So, it would be interesting to find what particular library is exporting > > the _rest* symbols this time, since libstartup-notification doesn't > > anymore. > > And the winner is libevent.
iceweasel built against 1.4.13-stable-1 which was built a long time ago, like libstartup-notification had, and 1.4.14b-stable-1 currently in unstable doesn't export the symbols. Same conclusion as with libstartup-notification: old toolchain bug. Still, I think it's wrong that a random library can highjack symbols that gcc uses to call its own stuff from libgcc. Are there actual legitimate uses of that "feature"? Mike -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110831053528.gc5...@glandium.org