p {margin-top:0px;margin-bottom:0px;}
unsubscribe - Andrew Choi( [email protected])
---------[
¹ÞÀº ¸ÞÀÏ ³»¿ë ]----------
Á¦¸ñ : Re: How Do I Debug This?
³¯Â¥ : 2010³â 1¿ù 06ÀÏ ¼ö¿äÀÏ, ¿ÀÀü 08½Ã 21ºÐ 37ÃÊ +0900
º¸³½ÀÌ : Jeremy H. <[email protected]>
¹Þ´ÂÀÌ : [email protected] (ruby-talk ML)
On Wed, Jan 06, 2010 at 07:59:34AM +0900, James Edward G. II
wrote:
> I'm getting an error in a test suite for an FFI project:
>
>
............................................................................................................................................ruby(1756)
malloc: *** error for object 0x101c39310: pointer being freed was not
allocated
> *** set a breakpoint in malloc_error_break to debug
>
> I assume I'm forgetting to free an allocated chunk of memory.
What's te best way to zero in on the issue?
>
> Is the breakpoint suggestion a gdb tip? Is there anywhere I could
go read about how to look into that?
>
> Thanks in advance for the advice.
>
> James Edward G. II
When I have something like this, I generally will compile a debug
(-g)
version of ruby and then run the spec/test via gdb to figure it out. Do
a stack
trace in gdb and look where the free is being called and go from there.
I'm guessing that this might be showing up in your new OklahomaMixer
project
and that this free might be happening in relation to a Tokyo Cabinet
call :-).
If that is the case, I'd also compile a debug version of TC for you to
use
with FFI, and you might need a debug version of FFI also.
enjoy,
-jeremy
--
========================================================================
Jeremy H. [email protected]
|
<br><br><a href="mailto:[email protected]"><img
src=“http://nametag.hanmail.net/3K3As7mKsYbV3qUGklp-lg00”
border=“0”>
