Re: Debug stepping speeds

Thanks for the reply. When the debug kicked into "overdrive", there were no changes to those tabs at top (Variable, Breakpoint, Monitor and Program were the only tabs up there, and it was on the Variable tab at the time). It just suddenly jumped from about two lines per second to ten, which matched the settings I gave it. I also added some additional monitoring of variables to add to the load yet it performed well. The only thing different? I had stopped, then restarted the debugger with the same configuration. I've done that numerous times before and got the same slow pace...but then yesterday, it was blazing, and it stayed that way for the afternoon, despite stopping and restarting several times. I will continue to document this to see if there is some key event I am triggering to cause this sudden burst. (I should also add about yesterday that, when it switched from one program to another during the debug, the level (or number) of variables undoubtedly changed, but it was still zipping along nicely.)

Ken

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Sean Kennedy
Sent: Tuesday, May 03, 2011 12:16 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debug stepping speeds


Hi Ken,

I am glad you like the Animated Step debug feature.
A common cause of a slower than desired stepping speed is having debug views open that require more data. If the Variables view is open, for example, then as part of each step, the debug engine needs to read the debug information for all the locals and send any changes back the UI.
Similarly for the Registers view.
If you are interested in local variable values (or registers) as part of your animated stepping session, you could try monitoring the specific variables (or registers) you want to see and then showing the Monitors view instead of the Variables view. That way, only the changes for the locals you have a direct interest in will have to be sent back to the UI.
Of course, even with every view but the Debug view hidden, the ability of the UI to issue the next step command is dependent on the remote engine replying to the current step request. Network and server load could be playing a larger part in the slowness than anything else.

I hope this information is helpful for you to optimize your Animated Step use!

Good luck.



Sean Kennedy
Client Engagements Leader: Rational Developer for Power
Software Developer: Rational Debug Technology



IBM Rational Software - IBM Toronto Software Lab I'm Speaking at
Phone: 905-413-4385 (Internal: 313-4385) Innovate 2011
Email: seanpk@xxxxxxxxxx
LinkedIn: seanpk

Innovate 2011, June 5-9: Software. Everywhere.





Learn more about Rational Developer for Power on the Find IBM Rational Debug
IBMRational youtube channel: Technology in:

AIX COBOL Development with Rational Developer for Rational Developer for
Power Power
C and C++ Development with Rational Developer for Rational Developer for
Power System z
Advanced Uses of Rational Developer for Power Rational Application
... and on developerWorks Developer
TPF Toolkit

Request Enhancements to Rational Developer for Power






Let your plans be dark and impenetrable as night, and when you move, fall like a thunderbolt.
-- Sun Tzu, The Art of War
This e-mail and attachment(s) may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this message is strictly prohibited. If received in error, please notify the sender immediately and delete/destroy the message and any copies thereof. Although Associated Banc-Corp and/or its affiliates (collectively "Associated") attempt to prevent the passage of viruses via e-mail and attachments thereto, Associated does not guarantee that either are virus-free, and accepts no liability for any damage sustained as a result of any such viruses. Any federal tax advice contained in this communication (including any attachments) is not intended or written to be used or referred to in the promoting, marketing, or recommending of any entity, investment plan or agreement, nor is such advice intended or written to be used, and cannot be used, by a taxpayer for the purpose of avoiding penalties under the Internal Revenue Tax Code