Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Crash if debugger open
Message
From
05/08/2003 12:35:04
 
 
To
27/06/2003 09:41:59
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00804339
Message ID:
00816944
Views:
40
I invoked SET STEP ON from in code to watch a few things happen. They happened correctly, and the program exitted normally, leaving the debugger open. When I clicked the X to close the debugger frame, C5. :/

>Also, it would help if we could some crash info from you.
>
>1. Go to Control Panel/Administrative Tools, and open Event Viewer. Look in your Application event log. You will see 2 events from the time of the crash with IDs 1000 and 1001, with the 1001 being newer. Please open the 1001 event, and you will see text like this:
>
>The description for Event ID ( 1001 ) in Source ( Microsoft Visual FoxPro ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 12697551.

The following information is part of the event: 36451244.

>2. Please send through the number at the end of that text in your event log item, which may sometimes be referred to as the 'bucket ID'.
>
>3. If you chose not to send in the report when you got the crash, you will still have an EventID 1000 from when the crash occurred. It will contain text like this: vfp8.exe, 8.0.0.2521, vfp8.exe, 8.0.0.2521, 0041863f

vfp8.exe, 8.0.0.2521, vfp8.exe, 8.0.0.2521, 003237ad.

>Send through this text if you don't have a bucket ID. Either of these can help us pin down the cause of the crash.

Hope this helps.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform