Hello Eddie,

Friday, October 15, 2004, 12:03:47, you wrote:


EC> Now my System is up and normal. But I want to find the proper file
EC> that was creating this high CPU. Therefore my request for your help -
EC> especially from RL (as it's actually there issue).

EC> I need to know which are the files that are restored under the "Global
EC> Options"? I want then restore those one by one and see what happens.
EC> Any idea?

GREAT work, Eddie.

I think the problem lies on corrupted value(s) in (probably) your
global options -- or, perhaps, an interaction between options. As
such, this should be opened as an issue in BugTrack, and the backup of
the Global Options attached to it.

The issue seems to be not what files are used when you restore it, but
what is in there. Whatever it is, a backup took it, and a restore used
it. So... RL should be able to look at the backup, and gather the
necessary data to find what values causes the high CPU.

Notice that this is not quite the same as finding the root cause but,
hopefully, they will be able to backtrack even more...

I still wonder why so many programmers nowadays do not put in an
extensive debug facility in their products, and give the users an
option for starting a debug trace. Yes, the code grows, but it is only
a resource impact (in terms of time and CPU usage) if the traces are
activated.

RitLabs -- please do yourselves, and us, a favour, and consider this
for a next release. Correctly implemented (and, please do not tell me
it's impossible: I have written a lot of code with trace embedded),
it helps the customer when hit by a reproducible issue, and helps
A LOT the fixer.

Alea jacta est. Let's now see how RL reacts.

-- 

 ..hggdh..

Using The Bat! v3.0.1.33 and BayesIt! 0.7.3 on Windows 2000 5.0 Build  2195
Service Pack 4

Attachment: pgporE5RyIhwc.pgp
Description: PGP signature

________________________________________________________
 Current beta is 3.0.2.1 Beta/1 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
IMPORTANT: To register as a Beta tester, use this link first -
http://www.ritlabs.com/en/partners/testers/

Reply via email to