19 Aug
2006
19 Aug
'06
9:56 p.m.
On Fri, 18 Aug 2006, Charles Henry wrote:
(I traced out the problematic statement by adding printf's in between statements) Once the program hits freebytes, it spits out "glibc detected: double free or corruption". any ideas? Chuck
Try two wonderful programs Valgrind and Valkyrie, which will find the problem at the moment it occurs, instead of after-the-fact like glibc's malloc/free do. This is because Valgrind runs all of the code in an emulator (to say things simply...) in order to check all memory accesses.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada