|
Home > Archive > Programming with dBASE > July 2005 > Memory Violation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Jim Dutton 2005-07-21, 8:23 pm |
| Since installing version 2.5 earlier today I have gotten frequent "memory violation" messages while I am debugging a program. I have never encountered this before, so it must be a new feature of 2.5. Any ideas as to what I can do to get rid of this anno
ying issue?
| |
| Ken Mayer [dBVIPS] 2005-07-21, 8:23 pm |
| Jim Dutton wrote:
> Since installing version 2.5 earlier today I have gotten frequent "memory violation" messages while I am debugging a program. I have never encountered this before, so it must be a new feature of 2.5. Any ideas as to what I can do to get rid of this an
noying issue?
It will go away in the next release, I believe. At least most of those
errors. There's some weirdness going on under the hood ... R&D has been
dealing with it.
Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/
*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase
| |
| Todd Kreuter [dBVIPS] 2005-07-22, 3:23 am |
| "Jim Dutton" <jtdutton@bu.edu> wrote in message
news:AaMozGjjFHA.2024@news-server...
> Since installing version 2.5 earlier today I have gotten frequent "memory
violation" messages while I am debugging a program. I have never
encountered this before, so it must be a new feature of 2.5. Any ideas as
to what I can do to get rid of this annoying issue?
Check your code for any division by zero. I was getting this error
frequently, finally determined that was the cause. It was not so obvious, as
the error popped up at various times after the division by zero occured.
There are other causes repored by others, one having to to with API externs
I believe.
Todd Kreuter [dBVIPS]
| |
| Jim Dutton 2005-07-22, 9:23 am |
| Now I am discovering that just adding "set step on" to a program to call the debugger often causes a crash.
Jim Dutton
===============
Ken Mayer [dBVIPS] Wrote:
> Jim Dutton wrote:
annoying issue?[color=darkred]
>
> It will go away in the next release, I believe. At least most of those
> errors. There's some weirdness going on under the hood ... R&D has been
> dealing with it.
>
> Ken
>
> --
> /(Opinions expressed are purely my own, not those of dataBased
> Intelligence, Inc.)/
>
> *Ken Mayer* [dBVIPS]
> /Golden Stag Productions/
> dBASE at goldenstag dot net
> http://www.goldenstag.net/GSP
> http://www.goldenstag.net/dbase
| |
|
| Jim,
Someone posted here that a msgbox just before the set step on can sometimes prevent that. I found it helped but not always.
Rick
Jim Dutton Wrote:
> Now I am discovering that just adding "set step on" to a program to call the debugger often causes a crash.
>
> Jim Dutton
> ===============
> Ken Mayer [dBVIPS] Wrote:
>
s annoying issue?[color=darkred]
>
|
|
|
|
|