99% (or more) of the time this is going to be your code. I would move forward
based on that assumption.
Found this that might help you:
http://stackoverflow.com/questions/1730180/is-this-kind-of-crash-report-useless
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced
There's no easy method of detecting memory corruption from inside your
own application, especially the memory that your application don't
control. You can use memory debuggers for that purpose. If you were on
Linux I would recommend to use valgrind. But I don't know if there are
any similar tools
But that would flag valid state changes just as much as it would flag corrupted
memory.
Rick
On Jul 19, 2012, at 11:15 AM, Black, Michael (IS) wrote:
> It could easiliy be expanded to look at the whole structure...
>
>
>
> Or just do an XOR checksum on the bytes in sizeof(sqlite3) and
Hmmm...somebody might need to point out what elements remain static.
So may not be able to do the whole structure like that.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
It could easiliy be expanded to look at the whole structure...
Or just do an XOR checksum on the bytes in sizeof(sqlite3) and compare that.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
5 matches
Mail list logo
