Runing IS5.53 Pro. Debugging an install. I've got GetEnvVar() putting the contents of Path into a STRING variable. The function succeeds (returns 0) but when I try to view the contents of the STRING in the debugger, I get a memory read error and have to terminate the install being debugged. It's not imperative to see the contents of the string but it does seem to be a bug in the debugger in allowing the user to view large(?) strings. And yes, I have a large Path, 909 characters but on 32 bit setups, STRINGs are supposed to hold 1024 characters.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Memory Read Error on STRING in debugger
Started by
jennetta
, Jun 13 2002 15:03
2 replies to this topic
Perotin
-
- Full Members
- 407 posts
Posted 13 June 2002 - 15:41
If the STRING length was exeeded, there would be an error 401 message.
Maybe you post the code lines which happen to crash?
Maybe you post the code lines which happen to crash?
Gruß / regards
Thomas
Thomas
jennetta
-
- Members
- 26 posts
Posted 13 June 2002 - 16:01
Thanks for your interest.
The code is really nothing much:
nResult = GetEnvVar("Path", szCurrentPath);
szCurrentPath is just a STRING. The problem only manifests when I try to view its contents in the debugger, otherwise the function in which the code resides does seem to work properly and nResult is being set to 0, to indicate success.
-Bill
The code is really nothing much:
nResult = GetEnvVar("Path", szCurrentPath);
szCurrentPath is just a STRING. The problem only manifests when I try to view its contents in the debugger, otherwise the function in which the code resides does seem to work properly and nResult is being set to 0, to indicate success.
-Bill
Bill