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 me much.. i'm assuming valgrind is better? i took a sneak peak at valgrind.. and it looked really complicated.. is it? do you have pointers about some light weight tutorials or intros? i found their documentation and tutorials a bit heavy handed. A On Sat, Jan 26, 2013 at 6:26 PM, Roger Binns [via SQLite] < ml-node+s1065341n66730...@n5.nabble.com> wrote: > -----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 SQLite is the victim of some other memory > mismanagement in your app and changing the SQL has just changed what code > will fall victim to it. > > It is a very good idea to run valgrind before proceeding. > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAlEEA6AACgkQmOOfHg372QSswACgoIg1jidTzar4EVVfQmFZlDwb > ZuAAn1iIuUz84T4Gpzgv2Q58U1zYq9MR > =z+X5 > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > [hidden email] <http://user/SendEmail.jtp?type=node&node=66730&i=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-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 memory deallocation, click > here<http://sqlite.1065341.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=66687&code=YWJkdWxsYWguYmFraGFjaEBnbWFpbC5jb218NjY2ODd8LTIwMjk1NDgyOTg=> > . > NAML<http://sqlite.1065341.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://sqlite.1065341.n5.nabble.com/using-the-same-sqlite-parameter-more-than-once-causes-premature-memory-deallocation-tp66687p66974.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
