Bauss:
Is there any way to track down access violations, instead of me
having to look through my source code manually.
I have a pretty big source code and an access violation happens
at runtime, but it's going to be a nightmare looking through it
all to find the access violation. Not to mention all the tests
I have to run.
So if there is a way to catch an access violation and find out
where it occured it would be appreciated!
This was discussed some times, and Walter is against this, but I
think he is wrong, and eventually things will change. So I think
this discussion should be brought to the main D newsgroup again.
Ideally in non-release mode D should put asserts where a access
violation could happen. But I don't know how much slowdown this
will cause. If practical real tests show that the slowdown is
excessive, then a compiler switch could be added to activate
those asserts.
Bye,
bearophile
