-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/13 06:01, abbood wrote:
> i tried using the memory diagnostics tools in Xcode/Instruments --
> Zombies, GuardMalloc, and Malloc Stack Logging.. but they didn't tell
> me much.. i'm assuming valgrind is better?
They are fairly lightweight and
be added to the discussion
> below:
>
> http://sqlite.1065341.n5.nabble.com/using-the-same-sqlite-parameter-more-than-once-causes-premature-memory-deallocation-tp66687p66730.html
> To unsubscribe from using the same sqlite parameter more than once causes
> premature memo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/01/13 23:45, abbood wrote:
> i fixed it!! you were right! it's not to do with the guts of sql..
> rather it's to do with my incorrect sql statement..
Huh? There is no SQL statement, valid or not, that can cause memory
errors. It looks like
er/SendEmail.jtp?type=node=66718=0>
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
>
> ------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://sqlite.1065341.n5.nabble.com/using-the-s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/01/13 17:37, abbood wrote:
> Btw I'm curious how did you find out about this auto release thing? Can
> you add more detail about that?
I used a debugger to set a breakpoint in malloc_error_debug as the message
says. That gave a stack trace of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/01/13 00:24, abbood wrote:
> then it crashes with the following error: malloc: *** error for object
> 0x9b6350: pointer being freed was not allocated *** set a breakpoint
> in malloc_error_break to debug
Coincidentally enough I am debugging
th the following error: malloc: *** error for object
0x9b6350: pointer being freed was not allocated *** set a breakpoint in
malloc_error_break to debug
any idea why?
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/using-the-same-sqlite-parameter-more-than-once-cause
7 matches
Mail list logo