-
I seems I forgot to include the new code in the previous version of this patch.
It is now included.
2009-10-18 13:14:34 UTC in Logging Framework for C
-
Logged In: YES
user_id=844843
The problem is that you did not use -D_REENTRANT when
compiling the file that contains the function main. When
this is done the bounds-checking code will become thread safe.
The -D_REENTRANT option MUST be used anyway when compiling
programs that use threads.
2005-02-17 17:20:57 UTC in boundschecking
-
Logged In: YES
user_id=844843
I seems I forgor the -g flag in some places when generating
the bounds-checking library. I will fix this in the
upcomming 3.4.2 release.
2004-09-06 20:42:20 UTC in boundschecking
-
Logged In: YES
user_id=844843
This will be solved in the upcomming 3.4.2 release. Sorry
that I missed this one when generating 3.3.4 and 3.4.0 and
3.4.1 patches.
2004-09-06 20:31:28 UTC in boundschecking
-
Logged In: YES
user_id=844843
This is working in the gcc 3.4.* version of the compiler.
So the solution is to update to the newer version.
2004-09-06 20:29:00 UTC in boundschecking
-
Logged In: YES
user_id=844843
This was done on purpose. We want to know as much as
possible about externel variables. This is why we put it in
the __bounds_private_statics tabel. This makes it possible
the compile one file with bounds-checking and another not.
If we see externs in the one compiled with bounds-checking
we know the size and this helps us finding errors.
I think the...
2003-12-13 22:21:29 UTC in boundschecking
