lite-C doesn't have bounds checking, so invalid array indices themselves (even negative ones) won't cause errors. But you could try the following in order to narrow down the problem:
Constantly check if ss_ledgendDeathsText == NULL. If true, log the memory locations of ss_ledgendDeathsText and all arrays, structs etc. in question. Then find the address that is closest to ss_ledgendDeathsText. This might be the evildoer.
Re: How to find out what function deletes my object
[Re: Myrkling]
#377044 07/09/1114:4307/09/1114:43
Still, the number of arrays and structs I have is immense. This will take some time to do...
Another thing: if I log the address of an array, it logs the beginning of the array, right? so if the array is pretty long, can I be sure that it is always in one piece?
~"I never let school interfere with my education"~ -Mark Twain
Re: How to find out what function deletes my object
[Re: Germanunkol]
#377047 07/09/1114:4807/09/1114:48
Another thing: if I log the address of an array, it logs the beginning of the array, right? so if the array is pretty long, can I be sure that it is always in one piece?
Physical probably not, but the OS will map one large chunk of virtual memory to the physical memory.
Shitlord by trade and passion. Graphics programmer at Laminar Research. I write blog posts at feresignum.com
