Re: Fw: Debugging - stopping at F-Spec -- WDSCI-L

Subject: Re: Fw: Debugging - stopping at F-Spec
From: Dave <dfx1@xxxxxxxxxxxxxx>
Date: Fri, 8 Jun 2012 13:19:18 +0200
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

2012/6/8 Paul Bailey <PaulBailey@xxxxxxxxxx>:

Karleen has the best option, IMO, because the additional *SrcStmt is very useful for working out which source line a runtime error appears on.

Hi Paul, what do you mean exactly by that?
I've often found the iodebug information useful when a program crashes
on i/o. With STRDBG you can use F15 to show the fields and step
through them to the one that is causing the problem. Is there an
equivalent in RDP?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Fw: Debugging - stopping at F-Spec , Paul Bailey

This mailing list archive is Copyright 1997-2025 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.