RE: UniDebugger in SB+
I don't use the dual session - it seems a little redundant. I have it setup to use the disk option for read/write which requires that I have the host session logged into the correct account in order to compile/catalog the program. To do this I change the view to host (so I can see the screen) and hit connect. That gives me the login prompt and I login (don't use a GUI terminal type) and from the menu I enter '0' to get to the UniData TCL prompt (:). If you run F5 the program it will only go into the debugger if you have a debug statement in the code. You can do an F8 to 'step into' the code. Each F8 will execute a line. This will update the edit window. If you change the view to 'debug' there is a watch window that you can add variables to using the 'quick watch' button - which will also allow you to view the values of variables. There are a couple different step buttons to 'run to cursor', 'step over' etc. It seems to work reasonably well (but then I haven't used the VB one much). What exactly were you unable to do? hth -- 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: Thursday, February 05, 2004 9:35 AM To: U2 Users Discussion List Subject: Re: UniDebugger in SB+ SNIP Colin- I'm not clear what exactly Dual session is about. I can click Compile, Catalog, or Run, and they work fine. However, the whole point of UniDebugger (from my perspective) is that it gives VB-like control over running code. I made some progress by changing the login script to only get to the unix shell. However, there is still some kind of hiccup where I click Step Into, then I have to click on the Dual Session and press Enter to make things move forward. Is there something I need to set differently? TIA, David Beahm -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: UniDebugger in SB+
I am having trouble using the step functions. In my scenario, I have a program open for editing: PRINT @TTY = :@TTY FOO = 1 DEBUG PRINT ALL DONE I save it (using the UniObjects option) and select Tools | Compile. I fill in my password and the login script runs: - unix username/password login - exit script menu to unix prompt - stop dual session - start UniData login script - SB username/password login, select Wyse60 terminal type, etc. - drop to : prompt per your suggestion The terminal window shows everything working fine. Pressing F8 once works perfectly -- the yellow arrow points to the first line, the terminal window shows the SETDEBUGLINE and RUN commnads. Pressing F8 again, the output from the first print statement shows but the yellow arrow in the editor disappears. Continuing to press F8 does nothing, however if I switch to Show Dual Session, press Enter, switch back, press F8, switch to Dual Session again, and press Enter again, something unclogs and the debugger commands that hadn't executed before suddenly run ($ and a \FOO for my watch) and the yellow arrow reappears. If I leave the Dual Session up, things continue to work (F8 moves the yellow arrow, etc.). When I press F5 to let the program run (after stepping thru the DEBUG statement) the dual session shows up at line 1 again in debug mode. I can manually type E to finish running the program, but I don't know why it ran again. I can flip back to the regular session and see what was output. Doesn't sound right to me. Is there something I need to do in Dynamic Connect's settings? Thanks, David Beahm [EMAIL PROTECTED] wrote: I don't use the dual session - it seems a little redundant. To do this I change the view to host (so I can see the screen) and hit connect. That gives me the login prompt and I login (don't use a GUI terminal type) and from the menu I enter '0' to get to the UniData TCL prompt (:). If you run F5 the program it will only go into the debugger if you have a debug statement in the code. You can do an F8 to 'step into' the code. Each F8 will execute a line. This will update the edit window. If you change the view to 'debug' there is a watch window that you can add variables to using the 'quick watch' button - which will also allow you to view the values of variables. There are a couple different step buttons to 'run to cursor', 'step over' etc. It seems to work reasonably well (but then I haven't used the VB one much). What exactly were you unable to do? hth -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: UniDebugger in SB+
It looks like it is getting a little confused. I've never had to use the dual session option. Pressing F8 steps through the code just fine for me. After you get the host window logged in can you choose compile and have the compile message show? I find it easiest to switch to host view (alt+v 3) so you can read all of the messages. I'm not sure if there is any difference when using uniobjects (as I couldn't get it to work as easily as disk). Perhaps the uniobjects connection is causing the issues with dual session. Can you use ftp? I'm running UniDebugger 1.2.3 hth -- 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: Friday, February 06, 2004 1:57 PM To: U2 Users Discussion List Subject: Re: UniDebugger in SB+ I am having trouble using the step functions. In my scenario, I have a program open for editing: PRINT @TTY = :@TTY FOO = 1 DEBUG PRINT ALL DONE I save it (using the UniObjects option) and select Tools | Compile. I fill in my password and the login script runs: - unix username/password login - exit script menu to unix prompt - stop dual session - start UniData login script - SB username/password login, select Wyse60 terminal type, etc. - drop to : prompt per your suggestion The terminal window shows everything working fine. Pressing F8 once works perfectly -- the yellow arrow points to the first line, the terminal window shows the SETDEBUGLINE and RUN commnads. Pressing F8 again, the output from the first print statement shows but the yellow arrow in the editor disappears. Continuing to press F8 does nothing, however if I switch to Show Dual Session, press Enter, switch back, press F8, switch to Dual Session again, and press Enter again, something unclogs and the debugger commands that hadn't executed before suddenly run ($ and a \FOO for my watch) and the yellow arrow reappears. If I leave the Dual Session up, things continue to work (F8 moves the yellow arrow, etc.). When I press F5 to let the program run (after stepping thru the DEBUG statement) the dual session shows up at line 1 again in debug mode. I can manually type E to finish running the program, but I don't know why it ran again. I can flip back to the regular session and see what was output. Doesn't sound right to me. Is there something I need to do in Dynamic Connect's settings? Thanks, David Beahm -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: UniDebugger in SB+
Confused is definitely the word for it. I switched to ftp, but no change. Save / Compile / Catalog all work fine, I can see the commands in the host window. My version is 1.2.2, so maybe that's the clue I need. This is from our latest install CD, but maybe I'll grab a new PE version of the client disk. Thanks, David Beahm [EMAIL PROTECTED] wrote: It looks like it is getting a little confused. I've never had to use the dual session option. Pressing F8 steps through the code just fine for me. After you get the host window logged in can you choose compile and have the compile message show? I find it easiest to switch to host view (alt+v 3) so you can read all of the messages. I'm not sure if there is any difference when using uniobjects (as I couldn't get it to work as easily as disk). Perhaps the uniobjects connection is causing the issues with dual session. Can you use ftp? I'm running UniDebugger 1.2.3 hth -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: UniDebugger in SB+
Javed- afraid CTRL T isn't doing anything for me. Colin- I'm not clear what exactly Dual session is about. I can click Compile, Catalog, or Run, and they work fine. However, the whole point of UniDebugger (from my perspective) is that it gives VB-like control over running code. I made some progress by changing the login script to only get to the unix shell. However, there is still some kind of hiccup where I click Step Into, then I have to click on the Dual Session and press Enter to make things move forward. Is there something I need to set differently? TIA, David Beahm [EMAIL PROTECTED] wrote: 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... -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: UniDebugger in SB+
Haven't used the Dual Session so can't offer any help on that but... Try Control T as the break key... -Original Message- From: David Beahm [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 5: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 Also, I've noticed that CTRL C is caught by the UniDebugger (which complains there is nothing selected). How can I interactively tell a program to break? Any suggestions? I'd really love to see this thing work, it would certainly be an asset. TIA, David Beahm -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
