Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

elronaldo

macrumors newbie
Original poster
Sep 22, 2008
23
0
What would cause the following error? Rather what would be the best way to pinpoint this issue? I have tried using malloc_history however that dumps a huge output in the Terminal and is hard to pinpoint the issue.

TestApp(2582,0xa068afa0) malloc: *** error for object 0x4d060f0: double free
*** set a breakpoint in malloc_error_break to debug

Thanks!
 

lawicko

macrumors member
Jul 17, 2008
44
0
I remember having similar error some time a go. From what I remember - debugger should show exact line where 2nd free is called. Did you try to debug?
 

elronaldo

macrumors newbie
Original poster
Sep 22, 2008
23
0
I remember having similar error some time a go. From what I remember - debugger should show exact line where 2nd free is called. Did you try to debug?

Hmm. Yes, the debugger is not breaking for these or showing any further information.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.