pavel,
>
> I suspect that "as soon as the application launches" means that no
> parallel threads are working yet (if they work already then look into
> what those threads are doing). Then the problem could be in some
> linking issues. E.g. you have some function that is named the same as
> some library function and so you and/or SQLite calls your function
> instead of from library. Or maybe some library you link with does
> something bad (and maybe in a different thread). Or it could be just
> different set of memory allocation calls so that in a different app
> hit to incorrect memory address doesn't touch another memory region
> which is corrupted in the initial app. Still running with valgrind
> could give some insights.
take a look at my last email about compilers.
and yes, no other threads are started, i'm doing this in a method
called directly from applicationDidFinishLaunching:, the first real method you
have access to after an app fires up.
if we decide to go down the road of trying to track the bug down in the
sqlite code, then i'll definitely check out valgrind.
thanks,
mickm
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
