Re: Error Log on debug (iSphere?) -- WDSCI-L

× 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.

I can watch it and see. How can I identify errors from iSphere?

-----Original Message-----
From: Tools/400 [mailto:thomas.raddatz@xxxxxxxxxxx]
Sent: Friday, February 16, 2018 11:45 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Error Log on debug (iSphere?)

Justin, please go to "Preferences - iSphere - Appearance" and uncheck "Show Eclipse error log on error". But on the other hand, what kind of error do you get logged from iSphere?

Thomas.

Am 16.02.2018 um 17:09 schrieb Justin Taylor:

Yesterday, I was getting an error in the iSphere Compare Editor when trying the "Open for edit" Mode. My iSphere wasn't current (I think I had v3 beta), so I updated to 3.2.2.r, and the error went away.

Today, the RDi Error Log view pops up every time I do a debug. I did a -clean startup and cleared my cache, but this persists. The last change was the iSphere update, so I suspect it as the culprit. Has anyone else seen this?

Here's the log entry:
!ENTRY com.ibm.debug.pdt.core 1 0 2018-02-16 10:02:56.128 !MESSAGE
[Thread-103] Logging engine trace to file C:\temp/epdcdump02.hex

Win7
RDi 9.6.0.1
iSphere 3.2.2.r

TIA

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.