Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-02-09 Thread Roger Binns
-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

Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-02-09 Thread abbood
humm... i think you are right.. the last time i spoke with you the error did indeed disappear.. but now it came back (embarrassed me infront of my client lol).. i tried using the memory diagnostics tools in Xcode/Instruments -- Zombies, GuardMalloc, and Malloc Stack Logging.. but they didn't tell

Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-01-26 Thread Roger Binns
-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 SQL

Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-01-26 Thread abbood
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.. i used MATCH instead of =.. for more details see the stack over flow response i made here http://stackoverflow.com/a/14534957/766570 A On Fri, Jan 25, 2013 at 9:18 PM, Roger Bi

Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-01-25 Thread Roger Binns
-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 a

Re: [sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-01-24 Thread Roger Binns
-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 thi

[sqlite] using the same sqlite parameter more than once causes premature memory deallocation

2013-01-24 Thread abbood
if create an sqlite statement that uses the same parameter more than once ie NSString* updateStmt = @"INSERT INTO search_email(..., subject, ...)" " SELECT ..., :subject, ...," " coalesce((SELECT search_email.threadID " " FROM search_email " " WHERE search_email.subject MATCH :