Access violation while the program was idle - not trace information to track down the bug

Question

I have a program that just popped up an AV. Until now the Eureka Log could find the source code line that generated the error but now it displays only this:

Acc         


        

Answer 1

That's what EurekaLog does when it has nothing to work with. You need to rebuild and have the linker produce a detailed map file. That's how it knows what to apply its stack trace to.