We have a posix mutli-threaded C++ program running on Linux 2.6.32, which core-dumps in one of the threads. Analysing the core file with gdb-7.2 corss-compiled, we see that the faulting instruction is here 0x11491178 <+208>: lwz r0,8(r9) and registers in the frame show: (gdb) info reg r0 0x0 0 …. [...] read more
Uninitialized variables may have indeterminate values, as this answer to an earlier question points out. Is there a way to specify this indeterminate data to, say, repeat 0xDEADDEAD? The indeterminate data is apparently compiler-specific, but it would always be nice to force it to be something easily recognizable. Are there [...] read more
Windows has an advanced function built-in that lets a user manually initiate a BSOD. It is a debugging tool used to halt the system in the event of (though not necessarily limited to) a hang or freeze. When used, it causes a BSOD with the string MANUALLY_INITIATED_CRASH1 and whimsical code [...] read more
We've made an Android and iOS app and send this through some testing. Our tests found no bugs however when sending it to the App store we got denied and returned a crashlog. I however can't find the bug with the information given. Can anybody help me translate this crashlog? [...] read more
My program after running for around few hours randomly crashes because of a segmentation fault. My environment is Ubuntu (Linux) When I try to print the data structure thats being accessed when it crashed the pointer is always pointing to invalid memory. (gdb) p *xxx_info[8] **Cannot access memory at address [...] read more