Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Crashing VFP from error handler
Message
From
17/12/2021 01:47:29
 
 
To
16/12/2021 14:59:26
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
01682978
Message ID:
01682984
Views:
55
>Running into something really weird that almost has to be a local configuration issue. I'm working on a large application that's using an error handler that originated in Stonefield AppMaker and has been enhanced a bunch over the years. A couple of weeks ago, we made a change to the underlying ErrorLog table (widened one field so we could put some additional data into it).
>
>Since then, when an error occurs during my testing, VFP crashes.When I'm lucky, first I see an error message on the line that inserts data into the errorlog table. The error message is:
>
>“There is not enough disk space for .”
>
>Yes, with nothing between the word "for" and the period. The line of code it appears on is:
>
>
>		insert into ERRORLOG ;
>              (DATE, TIME, USER, TERMINAL, CUSTOMER, ALIAS,;
>               RECNUM, KEYFLD, ERRMSG1, ERRMSG2, ERRMSG3, ACTION, ;
>				MEMVARS, DETAILS, CALLSTACK) ;
>		   values ;
>		      (date(), time(), gcUSER_NAME, SysZero(), space(len(customer)), lcALIAS, ;
>               lnREC, lcKEY, lcLINE1, lcLINE2, lcLINE3, 'REBOOT',;
>               '', m.lcDetails, m.lcStackInfo)
>
>
>If I resume from this point, VFP crashes. The error log says it's C0000094. (More often, I get the crash without the error message.)
>
>What makes this interesting is that my client (another developer) and his customers aren't having this problem. Errors are logged as they should be.
>
>I've tried deleting and recreating the ErrorLog table from scratch. The lcDetails variable can be huge; I've added code to limit it to 254 chars just for testing. No joy there, either. I've tried renaming my FoxUser file so a new one is created.
>
>This is really slowing down my debugging. Open to any ideas.
>
>Thanks,
>Tamar

You could try replacing the other values also with Dummy strings to see if it concerns one particular field or value that causes the crash. Or run the INSERT statement separately in test, I cannot imagine that it is the table itself since you re-created it already (otherwise I would have thought index corruption). Or do Append Blank and then a replace.
Christian Isberner
Software Consultant
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform