|
I have the same performance experience debugging RPG. The 'tool tips' also takes a long time. But I really like having my break points saved across compiles so I use any of the three debuggers depending on the situation. Phil > -----Original Message----- > From: code400-l-admin@midrange.com > [mailto:code400-l-admin@midrange.com]On Behalf Of jim essinger > Sent: Tuesday, January 08, 2002 4:50 PM > To: code400-l@midrange.com > Subject: Performance of the distributed debugger > > > Greetings! > > I have tried to use the distributed debugger, but the > response time when stepping thru the program was slow. I > had to go back to the interactive source debugger to get a > fast enough throughput. > > Using Win 2000 Pro (service pack 2) with V4R5 on the AS/400 > and V5R1 (Service pack 4) on the laptop. 256 meg of memory, > local TCP/IP connection. > > How can I speed up the debugger. I was watching some array > elements, and it seemed to have to refresh the whole array > every time I stepped the next insturction. BTW: I was > debugging a COBOL program at the time (shouldn't make any > difference). > > Thanks in advance. > > Jim Essinger > Senior Programmer/Analyst > Student Loan Fund of Idaho > esinger@fmtc.com > 208 - 452 - 4058 > _______________________________________________ > This is the CODE/400 Discussion & Support (CODE400-L) mailing list > To post a message email: CODE400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l > or email: CODE400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/code400-l. > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.