Ashok wrote:
Hi All,
Have to come across any such issues?
Most experienced developers have come across such issues. As Richard
suggested, you are likely seeing the effect of a heap corruption that is
occurring somewhat earlier than the "crashing" which finally reveals a
problem. His question, "Have you run your application using valgrind?"
merits your attention. If you do not yet use any tools for the early
detection of heap corruption, you should learn to do so if you are a
serious developer. If you are using such a tool to help diagnose this
particular problem, it would help others to help you if you were to say
so. If you cannot be troubled to use such a tool, it makes little sense
for others to speculate as to how your not-yet-shown code is corrupting
the heap upon which sqlite3DbMallocRaw() depends. To be blunt, your
hope that somebody will recognize and help cure your bug is unrealistic.
You have some work to do, and use of valgrind or a similar tool is the
best advice you are likely to get that will help you do that work.
Best regards,
--
Larry Brasfield
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
