Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Application error Log
Message
De
15/11/1999 17:02:58
 
 
À
15/11/1999 05:06:25
Information générale
Forum:
Visual Basic
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00290474
Message ID:
00291297
Vues:
27
>Yes, I did try to look at the NT Event Viewer Log but there is
>not nothing of the sort (I check with its logged time). Thanks
>
>>>I encountered the following error message, and wonder
>>>where can I find the Log File to view the error?
>>>
>>>"An application error has occured
>>>and an application error log is being generated
>>> ss24.exe
>>>Exception:access violation(0xc0000005),Address:0x00431926"
>>>

That's a memory access violation; something in your app tried to address something it didn't have the rights to access, or the address it referenced didn't exist. It's a trap at the OS level - if you're relying on an app-based error logging mechanism, it never will get there - NT terminates your application in an effort to protect itself and anything else that's running on the system.

If you need to debug in detail your best approach would be to run your app under the control of something like VC++'s debugger. It won't show you the line of code that was running as VB, but by examining the machine code, you might be able to figure out what seemed to be going on when it failed.

Using a commercial debugging aid like BoundsChecker may be helpful as well.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform