I made it through the complete parsing of a test source member without any
crashes.
Here is the change log for everything I had to do to get it to work.
Added config value asp_name to the iledconf table
Added support for the asp_name config value in the code when IFS paths are
made
iledcfg_h.rpgle
asp_name - Added to the config object
iledutil.rpgle
loadConfig - Added support for asp_name
rpgparser.rpgle
readSource - Added conditional inclusion of the asp name in the
built path
convertQsysPathToIfsPath - Added conditional inclusion of the asp
name in the
built path
convertIfsPathToQsysPath - Added a skip of the ASP as the first
token if it's
configured to be used
clparser.rpgle
readSource - Added conditional inclusion of the asp name in the
built path
Fixed bug with copy book source members that are wider than 100 bytes
rpgparser.rpgle
readCopybook - Data and other related variables changed from 100a to
200a
Observation: Each tag section requires at least one (non space) character
immediately
after the tag on the same line or else the program will crash
due to
index out of range
Example
value = %trim(%subst(%trim(src.commentline):%len
(%trim(config.tag_config)) +1));
For instance this format will cause the application to crash:
*
* @config
* These are my notes about the configuration.
*
Fixed by conditioning the substring of the config_value to ensure an
out of bounds
error cannot happen. This may need to happen in other areas too but
fundamentally
the program should not be allowed to crash because a comment format was
not followed.
Thanks,
Robert Newton
Estes IT
System Architect
804-353-1900 x2256
rnewton@xxxxxxxxxxxxxxxxx
From:
RNewton@xxxxxxxxxxxxxxxxx
To:
"ILEDocs" <iledocs@xxxxxxxxxxxx>
Cc:
"ILEDocs" <iledocs@xxxxxxxxxxxx>
Date:
06/14/2011 07:51 AM
Subject:
Re: [IleDocs] Help setting up environment for debugging ILEDocs call
Sent by:
iledocs-bounces+rnewton=estes-express.com@xxxxxxxxxxxx
I finally got the code compiled so that the objects match the source
for debug and found that it was a path issue.
In order for it to work on our box I had to add support for an ASP
name in the path.
I will be evaluating it today and will post my results for anyone
interested.
Thanks,
Rob Newton
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you are not the intended recipient or the person
responsible for delivering e-mail to the intended recipient, be
advised that you have received this e-mail in error.
On Jun 14, 2011, at 1:40 AM, "Mihael Schmidt" <mihael@xxxxxxxxxxxxxx>
wrote:
I have no idea atm.
But the line could be a lot simple.
fd = open (path : O_RDONLY);
That should do the same.
On 13.06.2011 23:02, RNewton@xxxxxxxxxxxxxxxxx wrote:
Ok, I realized that I was looking at the wrong source from SF.net.
Once I
switched to the source from the parser directory instead of the
ILEDOCS
directory, the source better matched the objects when in debug but
not
completely. It is off by a few lines in the main entry and off by
about 30
lines in the rpg parser module.
Despite that I have tracked the problem down to when the source
file is
opened in the readsource procedure.
===
fd = open( path : O_RDONLY :
S_IRUSR + S_IWUSR + S_IXUSR +
S_IRGRP + S_IWGRP + S_IXGRP +
S_IROTH + S_IXGRP);
===
I get back a -1 as the response but it does not provide any
information
about the error. I have checked the path that is built on the line
prior
and it is able to be opened directly from that path copied from
debug so I
know the path is good.
Any ideas?
Thanks,
Robert Newton
Estes IT
System Architect
804-353-1900 x2256
rnewton@xxxxxxxxxxxxxxxxx
--
This is the ILEDocs (IleDocs) mailing list
To post a message email: IleDocs@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/iledocs
or email: IleDocs-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/iledocs.
For 80 Years ? Delivering Solutions that Exceed Expectations.
This communication and any transmitted documents are intended to be
confidential. If there is a problem with this transmission, please contact
the sender. If the reader of this message is not the intended recipient,
or the employee or agent responsible to deliver it to the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.
midrange.com
