work it out. it's called debugging. brucee
On Jan 30, 2008 12:13 PM, Pietro Gagliardi <[EMAIL PROTECTED]> wrote: > In this case, it only told me where the program crashed, which told > me nothing on why (because a different line or a color image worked). > > > On Jan 29, 2008, at 5:46 PM, Russ Cox wrote: > > >> I get something that ends in "(double-free?)" and then the program > >> crashes, but something like > > > > This usually means you have freed the same pointer twice > > or you are passing a pointer to free that was not returned > > by malloc. If you run acid to get a stack trace to see the > > context of the free, that is often enough to identify the > > problem. > > > > % acid pid > > acid: stk() > > ... > > ^D > > % > > > > Russ > > > >
