|
| Environment:
Win2K
PB Enterprise 5507 (old)
ODBC
No PFC
Using Protection Plus security library
I have struggled mightily before posting. The problem is as follows:
I call functions in an external function library to construct a
formatted string to show software licensing information from a
licensing file. The string is formatted with concatenated ~r~n
literals to provide line feeds.
The string is composed correctly, as far as the debugger is concerned.
It may be 15 lines or so, maybe 40 characters per line, so assume
<=1000 characters altogether.
When this string comes back to the calling context as a return value
from a Powerscript function ".INFO()" which in turn calls the external,
it may or may not display before raising a GPF. I havge tried
displaying it with a MessageBox and by copying it to a datawindow and
by putting it in a multi-line edit, to no avail.
The thing seems really benign so I am very  as to why this
innocent little string report would cause the blowup. My sense is that
it may be because I am not autoinstantiating the user object where the
DLL lives that is involved, but creating it dynamically, or, that I am
overflowing some parameter limit for string calls. I do NOT allocate
the string with the SPACE function before making the call (didn't help
anyway).
Error was raised in PBVM90.DLL and appeared to involve some version of
strcat()...
|
|