× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.






Here is a possibility Ken.
Export your breakpoints so you don't lose them and then remove them all.
See if that speeds it up.


Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i



Phone: 1-905-413-3125 | Home: 1-905-854-6195
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: Canada



----- Forwarded by Edmund Reinhardt/Toronto/IBM on 03/11/2014 10:05 AM
-----

From: Daniel Craggs/Toronto/IBM
To: Edmund Reinhardt/Toronto/IBM@IBMCA
Cc: Alan Boxall/Toronto/IBM@IBMCA, Morris Kwan/Toronto/IBM@IBMCA
Date: 03/11/2014 10:03 AM
Subject: Re: Fw: [WDSCI-L] RDi 9.1 Debug Start Time 1:22


Hi Edmund,

This may be due to a load of deferred breakpoints being set before each
debug session.

Ask the customer to remove all the breakpoints set in the breakpoint view
(they can export them if they wish to use them later). Then try launching
another debug session. It might be worth collecting an EPDC trace at the
same time just in case this doesn't fix their problem.

Sametime me if you need help with this.

Daniel Craggs
Level 3 Service Developer
Rational Debugger




From: Morris Kwan/Toronto/IBM
To: Daniel Craggs/Toronto/IBM@IBMCA
Cc: Alan Boxall/Toronto/IBM@IBMCA, Edmund
Reinhardt/Toronto/IBM@IBMCA
Date: 03-11-14 09:59 AM
Subject: Fw: [WDSCI-L] RDi 9.1 Debug Start Time 1:22


Hi, Daniel

You just worked on a slow debugger startup issue. Could you take a look at
this one and see whether it is due to the same breakpoint problem?

Thanks,

Morris Kwan
Debugger Development
IBM Toronto Lab
Tel: (905)413-3729
Email: mkwan@xxxxxxxxxx

----- Forwarded by Morris Kwan/Toronto/IBM on 11/03/2014 09:57 AM -----

From: Edmund Reinhardt/Toronto/IBM
To: Alan Boxall/Toronto/IBM@IBMCA,
Cc: Morris Kwan/Toronto/IBM@IBMCA
Date: 11/03/2014 09:56 AM
Subject: Fw: [WDSCI-L] RDi 9.1 Debug Start Time 1:22


Any thoughts?



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i



Phone: 1-905-413-3125 | Home: 1-905-854-6195
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: Canada



----- Forwarded by Edmund Reinhardt/Toronto/IBM on 03/11/2014 09:52 AM
-----

From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: "WDSCI-L@xxxxxxxxxxxx" <WDSCI-L@xxxxxxxxxxxx>
Date: 03/11/2014 08:22 AM
Subject: [WDSCI-L] RDi 9.1 Debug Start Time 1:22
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Hi,

It seems that my debug in RDi 9.1 seems to take an awful long time...

Currently it takes well over 1-minute. I timed it with a stop-watch, and it
took 1-minute and 22-seconds to start up...

Is there a way to speed up debug? I am currently using the SEP Debug...

Once started, it is awesome of course. But, the start time seems really
slow...

Maybe there is a setting I am missing...

Please advise, if you know of way to speed up debug.

Thanks

-Ken Killian-

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.