Glenn (and Will and others),
Thanks for the responses. The issue that we are encountering, is
specifically
caused by a program WITH source code that was compiled and cataloged,
calling a subroutine that was compiled and cataloged on another system.
There is NO DEBUG statement in the original source that was stripped and
later installed as object only.
Here's what's going on:
ClientProgram
*all source is here
IF MyValue = "123XYZ" THEN
DEBUG
END
CALL VENDOR.PROGRAM(MyValue,MyResult) ;! NO SOURCE there
In the code above, if we encounter the DEBUG and continue, we have the
problem
conversely,
ClientProgram
*all source is here
IF NOT(ASSIGNED(MyValue)) THEN
CRT "MyValue is not assigned"
INPUT X
END
CALL VENDOR.PROGRAM(MyValue,MyResult) ;! NO SOURCE there
will also blow up in the debugger if MyValue is not assigned.
The apparent conditions then are::
If a DEBUG is encountered in the local code with source, and the program
calls a properly cataloged subroutine without source, the debugger goes into
a loop displaying an invalid path message based on the last line found in
the .O object code.
The same thing happens if a passed variable is unassigned and referenced in
the code, the debugger displays the invalid path message.
The code was initially created on a windows system
(c:\YourPath\YourAccount/ProgramFile/ProgramName)
Is it possible to create symbolic links on a Windows system (Win 2000, or
XP, XP-PRO or NT)?
The symbolic link sounds like a viable solution for unix installs.
Thank you
Lee Bacall
http://www.binarystar.com
Phone: +1 (954) 791-8575
Cell: +1 (954) 655-6581
----- Original Message -----
From: "Glenn Herbert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 17, 2004 9:17 AM
Subject: Re: [U2] Universe Debugger - compile from different path with
run-time issue
> At 05:29 PM 9/16/2004, you wrote:
> >My questions, are:
> >Is there a way to fix the last line of the OBJECT code?
> >
> >I don't mind creating a utility to modify the last line of the object,
but I
> >suspect that there is at least a CRC or byte count that might throw
things
> >off. We tried to modify the last line in the .O code pointing to the
> >original path, using the editor, but that does bizarre things, like
multiple
> >paths.
>
> You are correct. Editing in a new path would invalidate the stored
checksum.
>
>
> >or
> >
> >Is there some feature that can be turned on (or off) to prevent DEBUG
from
> >attempting to read the object pointer shown in the last line of the .O
> >entry?
>
> There is no way to prevent DEGUG from reading the pointer from the .O
> entry. However, since this is a UNIX system, I would create a symbolic
> link of the ORIGINAL path ' c:\binarystar\dist' that actually points to
the
> NEW path 'D:\UV\ACCOUNTS\Binarystar'. Give that a try and let us know
how
> you fare.
>
> Glenn
> -------
> u2-users mailing list
> [EMAIL PROTECTED]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
