David;
I use UniDebugger in a UD6/SB5.2/Win2K system. However, I don't use it on the "regular" SB code as that has to go through our version control s/w. I use it on stand-alone (usually conversion) unibasic routines.
I use the host view when connecting/logging in until I get down to the command line in the account I'm working in (not the TCL> prompt in SB). I did script part of the login but I move around into various accounts so I didn't do all of it. I've never tried the dual-session mode.
I found the easiest way to get "into" the debugger is to put a debug into the program then compile and run it from the UniDebugger menu. Then it will stop at the debug statement and you can do all of the "steps" to move around the code, put variables into the watch stack etc.
Hopefully, this will get you a little farther...
--
Colin Alfke
Calgary, Alberta Canada
"Just because something isn't broken doesn't mean that you can't fix it"
Stu Pickles
-----Original Message-----
From: David Beahm [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 04, 2004 3:13 PM
To: U2-Users
Subject: UniDebugger in SB+
I was inspired by a recent post to take another swing at getting
UniDebugger to work w/ our UD6/SB+5.2/HPUX system. I have scripted the
login, and can open, edit, and compile code. However, when I try to run
a program through UniDebugger, the output window shows
----- logging into Dual debugging session -----
----- login completed -----
...and nothing more happens. If I choose Session | Show Dual Session
then I see where something tried to execute tty and received "Not a verb"
<snip>
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
