I am testing a visual c++ application and testing how the application would respond if system and library calls return unexpected errors.
My question is could anyone please advise what cause a library call to return unexpected errors. Is it power failure or something similar.
Any help is most appreciated.
cause a library call to return unexpected errors. Is it power failure or something similar.
Why dont you try Security Inovation's, HoloDeck, http://www.sisecure.com/holodeck/holodeck-trial.shtml It can "Observe the behavior of your application as you isolate the most vulnerable areas."
Also look for articles section.
I am actually using Holodeck to test this. i have blocked access to a library call and the system besaved incorectly. However what I dont understand is in the real world , what would cause such a scenario to happen, is it a power failure, memory etc etc
DLL Hell is a common problem, this is why Java uses packages and C# uses assemblies.
the problem with testing is that you really don't know when or how a situation might arise. You have to have a good understanding of the technologies you're using.
As for power failure? Er, I think you might lack an understanding of how a computer works.
What you're looking for is "how does a DLL get corrupted."
A DLL is just a file, how can a file get corrupted?
Also, an exe might have been linked with a diff version of the library compared to the DLL that the exe is accessing at runtime. Therefore, improper installation might be at fault.
You should read up on how to develop a lib/dll then you'll have a better understanding of them, which in turn will allow you to develop better tests. Advance windowsNT by Ricter is a good start as NT is the technology that XP is built on.