Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Steve Langasek
On Wed, Sep 14, 2005 at 03:39:35PM +0200, Enrico Zini wrote: > On Wed, Sep 14, 2005 at 04:47:46AM -0700, Steve Langasek wrote: > [...really interesting and insightful explanation snipped...] > > So: g++ is embedding an unversioned weak symbol in the library in some > > cases, which causes the lin

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Daniel Jacobowitz
On Wed, Sep 14, 2005 at 04:47:46AM -0700, Steve Langasek wrote: > so, the problem is caused by template instantiation shoving > this symbol into the library that uses it > the two possible solutions are (a) stop doing that, or (b) > version the symbol > so that's a g++ bu

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Enrico Zini
On Wed, Sep 14, 2005 at 04:47:46AM -0700, Steve Langasek wrote: [...really interesting and insightful explanation snipped...] > So: g++ is embedding an unversioned weak symbol in the library in some > cases, which causes the linker to resolve it to the version from the lib > used by the app, not

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Steve Langasek
On Wed, Sep 14, 2005 at 02:39:55AM -0700, Steve Langasek wrote: > On Wed, Sep 14, 2005 at 09:33:17AM +0200, Enrico Zini wrote: > > > On Tue, Sep 13, 2005 at 08:31:55PM +0200, Enrico Zini wrote: > > > > > > > > Applications linked with libstdc++5 and using GTK segfault when using > > > > SCIM[1] as

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Steve Langasek
On Wed, Sep 14, 2005 at 09:33:17AM +0200, Enrico Zini wrote: > On Tue, Sep 13, 2005 at 12:12:13PM -0700, Steve Langasek wrote: > > On Tue, Sep 13, 2005 at 08:31:55PM +0200, Enrico Zini wrote: > > > > > > Applications linked with libstdc++5 and using GTK segfault when using > > > SCIM[1] as input m

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-14 Thread Enrico Zini
On Tue, Sep 13, 2005 at 12:12:13PM -0700, Steve Langasek wrote: > On Tue, Sep 13, 2005 at 08:31:55PM +0200, Enrico Zini wrote: > > > > Applications linked with libstdc++5 and using GTK segfault when using > > SCIM[1] as input method, and neither GTK nor SCIM nor the apps seem to > > be to blame. >

Re: Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-13 Thread Steve Langasek
On Tue, Sep 13, 2005 at 08:31:55PM +0200, Enrico Zini wrote: > > Applications linked with libstdc++5 and using GTK segfault when using > SCIM[1] as input method, and neither GTK nor SCIM nor the apps seem to > be to blame. > > Since various days I've been experiencing weird and annoying crashes

Apps linked with old libstdc++ dlopening modules linked with the new one

2005-09-13 Thread Enrico Zini
Hello, Applications linked with libstdc++5 and using GTK segfault when using SCIM[1] as input method, and neither GTK nor SCIM nor the apps seem to be to blame. Since various days I've been experiencing weird and annoying crashes on openoffice and epiphany. I was kind of ignoring them, but now