Hi,

I am trying to debug a JAL script at home which I have transferred from my Work environment

24x7 version is 3.4.16 on both systems.

When I try to set breakpoints in the script code I get an error telling me that
Breakpoints can only be set on lines containing executable code (or similar words)

I have tried reinstalling the 24x7 setup completely but still no luck....

Help please....

Jim

You are not using pcAnywhere by any chance, are you?

: Hi,

: I am trying to debug a JAL script at home which I have transferred from my
: Work environment

: 24x7 version is 3.4.16 on both systems.

: When I try to set breakpoints in the script code I get an error telling me
: that
: Breakpoints can only be set on lines containing executable code (or similar
: words)

: I have tried reinstalling the 24x7 setup completely but still no luck....

: Help please....

: Jim

: You are not using pcAnywhere by any chance, are you?

NO I'm not :(

The reason for pcAnywhere question is a known bug in pcAnywhere screen driver that confuses the Debugger and makes it think the cursor is always outside of the valid line range. I wonder if your screen driver creates the same effect. Can you reproduce this problem on other computers?

: NO I'm not :(

: The reason for pcAnywhere question is a known bug in pcAnywhere screen driver
: that confuses the Debugger and makes it think the cursor is always outside
: of the valid line range. I wonder if your screen driver creates the same
: effect. Can you reproduce this problem on other computers?

Haven't been able to try yet will post back as soon as I can.

I'f I reset screen to default VGA - for example - should that be a valid test also ?

Jim

I am not sure it is a VGA issue. In case with pcAnywhere the problem is casued by the display driver no reporting correctly mouse pointer position.

Instead of doubleclicks try using F8 hot key to toggle breakpoints.

: Haven't been able to try yet will post back as soon as I can.

: I'f I reset screen to default VGA - for example - should that be a valid test
: also ?

: Jim

: I am not sure it is a VGA issue. In case with pcAnywhere the problem is
: casued by the display driver no reporting correctly mouse pointer
: position.

: Instead of doubleclicks try using F8 hot key to toggle breakpoints.

Hi F8 - no difference :(

SWapped to latest official ATI RAdeon drivers from 3rd part drivers - no change.....

Help !!!

Jim

: The reason for pcAnywhere question is a known bug in pcAnywhere screen driver
: that confuses the Debugger and makes it think the cursor is always outside
: of the valid line range. I wonder if your screen driver creates the same
: effect. Can you reproduce this problem on other computers?

Haven't been able to try yet will post back as soon as I can.

I'f I reset screen to default VGA - for example - should that be a valid test also ?

Jim

I don't think we can help here. This poblem is somehow related to the video driver. Previously it has been reported only in situation when 24x7 is run in a psAnywhere session. No solution have been found so far. Please use alternative methods. You still should be able to do step-by-step debugging, insert debugging MessageBoxes and use the script trace feature insead of the inteructive debugger. Of course all of these options can be used separatelly or used at the same time.

: Hi F8 - no difference :(

: SWapped to latest official ATI RAdeon drivers from 3rd part drivers - no
: change.....

: Help !!!

: Jim

Not likely. It could be screen resolution, could be font size, could be anything else that makes the driver "think" that the cursor is outside of the screen. I wander if the current cursor position is displayed correctly in the right-down corner of the editor/debugger window. How does it look? What about the editor? Can you use block operations such as block indent, block comment, unindent, etc?
: Haven't been able to try yet will post back as soon as I can.

: I'f I reset screen to default VGA - for example - should that be a valid test
: also ?

: Jim