Subject |
Re: Error internal stack underflow |
From |
Lee Grant <camilee@nospam.comcast.net> |
Date |
Sat, 10 Aug 2024 04:37:59 -0400 |
Newsgroups |
dbase.getting-started |
Mark,
You can try this site for a fairly interesting discussion of debugging
Stack Underflow conditions.
https://www.codingdrills.com/tutorial/stack-data-structure/debugging-stack-undeflow-errors
And this description by Microsoft Learn:
https://learn.microsoft.com/en-us/cpp/sanitizers/error-stack-buffer-underflow?view=msvc-170
Worse come to worse, this could almost sound like the problem with the
_sql files, is the dBASE set up, perhaps, meaning a stack for keeping
track of these files, and it might trigger this condition. Not sure,
just spitballing here, since it could have done some damage to stack
when it hits it or tries to save it, or other variables that the program
kept.
Lee
On 8/7/2024 3:38 PM, Mark wrote:
> Have been supporting a Plus app in multiple locations for over 10 years. Sometimes get the fatal error - Internal Stack Underflow. I found the reason involves _qsql files. These are typically temporary files, but they can accumulate if the app crashes. If they accumulate beyond about 1000 this error will occur.
>
> I added a function in the app logoff code to cleanup these files and that has helped. But still getting this error for other unknown reasons.
>
> While ON ERROR catches most other errors it does not catch this one. Anyone know of a way to catch this? A TRY/Catch would probably work but this error can pop up anywhere and no way to locate the specific code where it occurs.
>
> In a search of this NG Mattia suggested - Try change the address inserted in SHAREDMEMLOCATION (BDE configuration). Have tried this but no joy.
>
> Any ideas appreciated.
|
|