[Xcb] xcb/libxcb git commit 46413cd85
Jeremy A. Kolb
jkolb at brandeis.edu
Wed Dec 12 06:45:39 PST 2007
On Wed, 12 Dec 2007, Matthias Hopf wrote:
> On Dec 11, 07 19:14:50 -0500, Peter Harris wrote:
>> What happens on Linux if you have library A statically linked against
>> uClibc, and library B dynamically linked against glibc? How does your
> That is the main reason why you don't mix dynamic and static linking.
> And why you don't link libc statically. This is just asking for trouble.
> Not only regarding malloc/free.
> I very much agree with Bart that we should not make the live for broken
> link models easy by making it harder for everybody else. Especially as
> you cannot be sure when calling free() on a pointer that it has been
> allocated within your scope and not outside (strdup etc.).
>> It's worse on Windows, where the malloc/free you get with a debug build
>> is incompatible with the regular malloc/free. This means that, if you
> OMFG. How broken is that?
I've actually been dealing with this on windows at work. It's extremely
painful and can be difficult to track down. And I agree, let's not
encourage such behavior.
More information about the Xcb