Re: Weird Error... Can't Debug -- RPG400-L

Subject: Re: Weird Error... Can't Debug
From: Adam Glauser <adamglauser@xxxxxxxxxxxx>
Date: Thu, 10 Apr 2008 09:08:13 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Mike wrote:

I am working through a problem right now. I have a program that calls a
subprocedure, that calls a second subprocedure. Both of these subprocedures
have worked in the past and I have not made changes to them. I just
recompiled everything just to be sure. I run it in WDSc Service Entry Point
debugger and it appears that the call to the second subprocedure bombs out.

Did you try stepping through both subprocedures to see where the problem lies? If you have:

pgmA --calls--> subProcA --calls--> subProcB

You can set your SEP on pgmA, then on the suspect call to subProcA choose 'Step Into' instead of 'Step over'.

Follow-Ups:

Re: Weird Error... Can't Debug , Mike

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.