Home > Archive > Clipper > July 2007 > vm integrity failure
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]
| Author |
vm integrity failure
|
|
| Dr. Peter Wiegand 2007-06-17, 7:55 am |
| Hello!
A big application with Clipper 5.2e and Blinker 7.0 breaks with "vm
integrity failure".
The bug disapears, when I reduce the source-code, no matter on which place.
It seems to be a size-problem.
With google I found many suggestions to solve the problem, but no solution
for my problem.
Any suggestions?
| |
| N:dlzc D:aol T:com \(dlzc\) 2007-06-17, 9:55 pm |
| Dear Dr. Peter Wiegand:
"Dr. Peter Wiegand" <dr.peter.wiegand@t-online.de> wrote in
message news:f530di$dcs$00$1@news.t-online.com...
> Hello!
>
> A big application with Clipper 5.2e and Blinker 7.0 breaks
> with "vm integrity failure".
>
> The bug disapears, when I reduce the source-code, no
> matter on which place. It seems to be a size-problem.
>
> With google I found many suggestions to solve the
> problem, but no solution for my problem.
>
> Any suggestions?
What operating system?
Compile your code into multiple executables, just like in the
"bad old days".
Move common functions into an external library (DLL or such)
Switch to:
www.xharbour.org
David A. Smith
| |
| Dr. Peter Wiegand 2007-06-18, 9:56 pm |
|
"N:dlzc D:aol T:com (dlzc)" <dlzc@aol.com> schrieb im Newsbeitrag
news:7Rddi.467858$115.310602@newsfe10.phx...
> Dear Dr. Peter Wiegand:
>
> "Dr. Peter Wiegand" <dr.peter.wiegand@t-online.de> wrote in message
> news:f530di$dcs$00$1@news.t-online.com...
>
> What operating system?
>
> Compile your code into multiple executables, just like in the "bad old
> days".
>
> Move common functions into an external library (DLL or such)
>
> Switch to:
> www.xharbour.org
>
> David A. Smith
Dear David A. Smith
Thank you for your suggestions.
The "vm integrity failure" occurs under Windows Xp, most probably as well
under all other Windows-versions and under DOS.
I already deliver an xBase++-application. Here the problem does not exist.
But many customers still prefer the DOS-application.
The idea with multiple executables works, but wirh bad performance. I think,
this will be the preliminary solution.
I have no experience with DLLs under clipper.
With xHarbour-DOS I fear the same problems with big applications as with
clipper/blinker.
Thanks also to "alcisoft". He/She suggestest Blinker 6.0 and/or clipper53. I
did not yet test these suggestions.
Peter Wiegand
| |
| N:dlzc D:aol T:com \(dlzc\) 2007-06-18, 9:56 pm |
| Dear Dr. Peter Wiegand:
"Dr. Peter Wiegand" <dr.peter.wiegand@t-online.de> wrote in
message news:f56vgl$d5m$00$1@news.t-online.com...
>
> "N:dlzc D:aol T:com (dlzc)" <dlzc@aol.com> schrieb im
> Newsbeitrag news:7Rddi.467858$115.310602@newsfe10.phx...
>
> Thank you for your suggestions.
>
> The "vm integrity failure" occurs under Windows Xp, most
> probably as well under all other Windows-versions and
> under DOS.
OK.
> I already deliver an xBase++-application. Here the
> problem does not exist. But many customers still prefer
> the DOS-application.
>
> The idea with multiple executables works, but wirh bad
> performance. I think, this will be the preliminary solution.
Only if necessary.
> I have no experience with DLLs under clipper.
Neither have I. But you can export common routines from your
code into DLLs with xHarbour.
> With xHarbour-DOS I fear the same problems with big
> applications as with clipper/blinker.
xHarbour / Windows (can still look just like DOS, and act like
DOS) will not have this problem, and can be a single executable.
Does the client have Windows on the machines, or just DOS?
> Thanks also to "alcisoft". He/She suggestest Blinker 6.0
> and/or clipper53. I did not yet test these suggestions.
Both still available for sale...
David A. Smith
| |
| Stephen Quinn 2007-06-19, 9:55 pm |
| Peter
[color=darkred]
> Thanks also to "alcisoft". He/She suggestest Blinker 6.0 and/or clipper53. I did not yet test
> these suggestions.
Going backwards with the linker (V7->V6) probably won't fix the problem, Clipper 5.3 would help with
memory management.
http://www.grafxsoft.com
Can you show us your link script.
Do you have any .obj files over 64K in size??
> With xHarbour-DOS I fear the same problems with big applications as with clipper/blinker.
Unikely as they'll 32bit apps not 16bit ones.
CYA
Steve
| |
| Dr. Peter Wiegand 2007-06-24, 3:55 am |
| Hallo Steve
Thank you for your suggestions.
Here is my link script:
blinker incremental off
blinker executable extended
blinker executable alignment 128
blinker message noblink
.... [about 50 OBJ-files]
file k:\objbli\errorsys
file k:\objbli\getsys
file k:\objbli\rddsys
file ctusp
file ctintp
search blxratex
search blxclp52
library clipper
library ctp52
library extend
library dbfcdx
library terminal
library lfn
library ll
library nanfor
library cpmi
output h:\a\apwxms
There are about 20 OBJ-files greater than 65K, the biggest is 340K.
The xHarbour 32bit programs are Windows-programs, I still need original
DOS-programs.
I still think the best solution is to use multiple exe-files. This works but
with bad performance.
Peter
"Stephen Quinn" <stevejqNO@SPbigpond.netAM.au> schrieb im Newsbeitrag
news:9sSdi.16254$wH4.4712@news-server.bigpond.net.au...
> Peter
>
>
> Going backwards with the linker (V7->V6) probably won't fix the problem,
> Clipper 5.3 would help with memory management.
> http://www.grafxsoft.com
>
> Can you show us your link script.
> Do you have any .obj files over 64K in size??
>
> Unikely as they'll 32bit apps not 16bit ones.
>
> CYA
> Steve
>
>
| |
|
|
|
|
|
dam-hussein-execution.org/court-