Re: Debug - Step Over...

Or you can right click on the line after the exsr and choose 'run to 
location'.

Matt Hopkins 
Sr. Programmer/Analyst 
Web: www.pdpgroupinc.com 
Email: MWHopkins@xxxxxxxxxxxxxxx 
Office: 410-584-0330 
Fax: 410-584-0336 





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/18/2006 03:31 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: [WDSCI-L] Debug - Step Over...

From: Turnidge, Dave

It was my understanding that "Step Over" in debug would SKIP the line
you were on; in other words, NOT go down into an EXSR, but continue
debugging with the next line AFTER the EXSR.

No, step over steps over calls to procedures and other programs.

When I "Step Over", it actually steps INTO, and I process the
subroutine...

Subroutine are not seen as procedures, but simply as gotos.  A step over a
GOTO will take you to the corresponding TAG statement.

Have I got something set wrong, or is this a bug that needs fixing?

Neither.  It's just the way it works.  I often wish that subroutines were
handled the same way as procedures, but they aren't.  My guess is that 
they
compile down to a GOTO and the debugger can't tell the difference.  But in
any case, the only way to not execute the lines of a subroutine is to
actually set a breakpoint on the line after the EXSR and do a Resume.

Joe