Re: Global variable in static library - double free or corruption error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 21 Oct 2010, Alexey Skidanov wrote:

Actually, you claim that if some static library defines some global variable,
then it should NOT be linked with more then one shared library.

Static libraries should only be linked with the executable. Shared objects are perfectly fine with undefined symbols. (Of course this is only a general rule, there can be good reasons to ignore it)



On Thu, 21 Oct 2010, Jeffrey Walton wrote:

In essence, the rule creates "Shared (Global) Data Segments" in the
Microsoft world. Those things are quite dangerous (because one process
can cause another to crash)

Er, I don't know about shared global data segments, but in this thread there is no mention of crossing the process boundary, only merging 2 variables in a given process.

--
Marc Glisse


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux