Difference in compile limitations

[Chris Kelleher]

Has anyone experienced a "difference" in the way RTB compiles a program
and a native progress session does ?

We have following problem that a (quite large) program does compile using
the native progress editor, but when compiled using RTB , it gives
us a "debugger segment exceeded" compile error.
It seems that the segment limitations are a little bit lower using RTB ?

The same connection/startup parameters were used for the progress editor
as for the roundtable client.

Does anyone has a workaround for this other than modifying the program ?

Version used: RTB 8.3A , progress 8.3A for Windows


Thanks for your help .


Jurgen Van Bouchaute

ICSAT nv.
Plantin & Moretuslei 220
B-2018 Antwerpen
Tel: 03/270-97-80
Fax: 03/270-97-81
E-mail: jvb@icsat.com
visit us at : http://www.icsat.com

 

[Chris Kelleher]

Jurgen,

You should remeber that Roundtable requires that you doa cmpile with Xref
for objects to be up to date. Therefore, you should be comparing the
compilation that you are doing with an Xref compile from a Progress session.
Roundtable is really just using a standard Progress compile parameter with
some extra options (Xref, listings etc. depending on your set-up).

My guess is that if you try and compile from Progress with the Xref option
then you will see the same error.

BTW - You should upgrade your Roundtable version to 8.3B + the latest patch
8.3B02. Order the version upgrade from Progress, or download it from www.roundtable-tsms.com. The patch can also be downloaded from this site.

HTH - if not let me know.

Thomas
___________________________________
Hansen IT Consulting
Frilandsvej 85
9800 Hjørring
Denmark

Tel.: +45 98 90 49 16
Fax.: +45 98 90 49 17
Mobile : +45 20 16 19 29

E-mail : thomas@hansenit.dk
Web : www.hansenit.dk
__________________________________
StarBase Corporation StarPartner and
Certified Roundtable Consultant

*** COMING SOON - Future Proof RAD Progress Development ****
!! Astra Development Framework and AstraGen Global Application Module !!!

 

[Chris Kelleher]

Jurgen,

The other difference that you might try in your test of the regular compile,
is the fact that the Roundtable database is connected. This should not
effect the outputted r-code but does take additional resources. In some
cases you need to increase your hash table to support the additional
database.

Do you get the error when compiling the object by itself, or only through
Selective Compile? The Selective Compile process would take up additional
memory, which could be the cause of your problems.

HTH

Nathan Noll (817) 284-8680
NCS Fax (800) 538-7510
Certified Roundtable Consultants nathan@nollc.com

Check out F1 an integrated Change Request System that works
with Roundtable! www.nollc.com/f1

 

[Chris Kelleher]

Jurgen,

A "difference" is due to the PROPATH difference.
Debugger segment stores (in the r-code's tail) the paths to the include
files (including the path to the procedure itself) as they were used at
compile time.

If, for example, you PROPATH containes the fully specified paths while you
compile programs using RTB and only relative paths while you compile from
Editor then the debugger segment sizes will differ.

HTH,
George Potemkin
CSBI EE, S.-Petersburg, Russia