[Implemented] More information for "Invalid memory access"

Trond · Post by **Trond** » Fri Nov 03, 2006 7:32 pm

It would be good if the debugger could give some more information than simply "invalid memory access". For example what address and module tried to access what access.

I am wrestling with some threads in dlls at the moment (so far the threads are winning) and "someone" are stealing my linked lists. Apparently at a ProcedureReturn but probably at some different place in my code.

Ollivier · Post by **Ollivier** » Tue Sep 04, 2007 8:02 pm

Yes it's a good idea!

Now, I need to know if the memory access into an adress is valid or invalid.

SoulReaper · Post by **SoulReaper** » Tue Sep 04, 2007 9:23 pm

Hello and Yes I agree that would be a great idea...

Maybe it will be done one day soon

Post by **freak** » Mon Sep 24, 2007 11:53 pm

It is implemented for the next beta. Displays the address and if it was a read or a write.
This is Windows only though. Dunno if i can get this info on the other OS.

Kaeru Gaman · Post by **Kaeru Gaman** » Tue Sep 25, 2007 12:32 am

good news so far.

...I'm sure on the other OSs the information is somewhere there, too.

seems you have to crawl your way though some API-dungeons...
*me hands a Torch and a Sword to freak* carry on...

Ollivier · Post by **Ollivier** » Wed Oct 03, 2007 5:21 pm

2Freak

Thanks! I didn't see your answer very early... I'll often use this new functionality. It allows a program staying stable during a scan for example.