Re: Shared object compiled with g++ is not unloaded

2015-05-05 Thread Jakub Jelinek
On Tue, May 05, 2015 at 09:01:03PM +0300, Max Dmitrichenko wrote: > So, really no ideas on this issue? Or this behavior is considered normal? It is not a bug, it is how STB_GNU_UNIQUE symbols work. With gcc 4.8.4, or 4.9.2, 5.1 or trunk you can actually use -fno-gnu-unique if you are ok with its c

Re: Shared object compiled with g++ is not unloaded

2015-05-05 Thread Max Dmitrichenko
So, really no ideas on this issue? Or this behavior is considered normal? 2015-04-26 1:38 GMT+03:00 Max Dmitrichenko : > Hi all! > > I've faced with strange behavior when I investigated a bug on a rather > new distros of Linux. I'm not sure that it is a bug of gcc, but may be > someone can bring s

Shared object compiled with g++ is not unloaded

2015-04-25 Thread Max Dmitrichenko
Hi all! I've faced with strange behavior when I investigated a bug on a rather new distros of Linux. I'm not sure that it is a bug of gcc, but may be someone can bring some light to it. So, my project heavily uses plugins which are dynamically loaded with dlopen() and unloaded with dlclose() func