In ILE RPG I've seen this behavior when modules and programs have been
optimized.

-----Original Message-----
From: c400-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx
[mailto:c400-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx] On
Behalf Of Lindbom, Joakim
Sent: Wednesday, May 10, 2006 7:03 AM
To: C programming iSeries / AS400
Subject: [C400-L] ILE source debugger problem



Hi!

I have a severe problem with the ILE source debugger. The debugger
doesn't follow the program logic! There's no warning that there's a
source mismatch.

An example:

1       printf ("argc: %d", argc);
2       if (argc < 3 || argc > 4) {
3               sprintf (sText, "Internal failure in trigger program
(KOF04C). Abending!");
4               sprintf (lText, "Usage: CALL KOF04C partner library
filename <member>\nIf member not passed, *ALL will be used");
5               AddLogText (&Lh, "main", SEV_FATAL, sText, lText);
6               exit(1);
        }
7       ExtendString (sPartner, argv[1], sizeof(sPartner));
8       ExtendString (sLibrary, argv[2], sizeof(sLibrary));
9       ExtendString (sFile,    argv[3], sizeof(sFile));

In this example argc=2 and the expected flow would be: 1, 2, 3, 4, 5, 6
but what happends is 1, 2, 9

Any clues? I don't expect this to be C specific, I've seen the same with
ILE RPG


/Joakim

This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.



This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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