Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Log view - Analyze selection: 90% CPU usage
Log view - Analyze selection: 90% CPU usage [message #107820] Wed, 08 August 2007 11:23 Go to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi everybody,
I experienced some trouble using log view and symptom catalogs.
I'm runnning Eclipse 3.3.0 with TPTP 4.4.0.2 all-in-One on Linux SuSE 10.1.
I am following the tutorial published on TPTP site, so I am tring to
analyze the log file generated by the sample application.
I firstly imported the symptom catalog provided in the zip file, then I
ran thesample web-app to generate some log messages. After that, I stopped
the server and terminated the profiler. Then I opened the "Profiling and
Logging" perspective and entered the "Log Navigator Section": the fresh
new log and the symptom catalog I had imported were there. Therefore, I
opened the log file, then I right-clicked on a message and I selected
"Analyze Selection". The event was correctly analized and each field was
properly reported. On the other hand, a progress bar labeled "Analyzing"
appeared at the bottom of the window, on the right side: it is a 3-ticks
bar, but it kept stuck on the first tick. I opened the system performance
monitor and I found that Eclipse was using 90% of CPU time: the refresh of
Eclipse UI was really slow (half a minute to repaint the UI). I had been
waiting for a minute hoping something might change, but: CPU usage was
always between 80 and 90 percent; the progress bar was still labeled
"Analyzing" and was still on the first tick; no useful
information/solution came from the symptom catalog (it should have
appeared "Do not let Harm put code on your project").
It seems that nobody else experienced something like that: I couldn't find
anything similar on google and on this mailing list. Maybe it is an error
of mine, but I cannot sincerely imagine what could go wrong in following
few easy steps.

Hoping not to having bothered you with useless doubts,
I thank you for your attention.
Alessandro
Re: Log view - Analyze selection: 90% CPU usage [message #107925 is a reply to message #107820] Wed, 08 August 2007 15:41 Go to previous messageGo to next message
Alex Nan is currently offline Alex Nan
Messages: 29
Registered: July 2009
Junior Member
Hi Alessandro,

I am sorry to hear that you had trouble running a TPTP tutorial, in order to
understand you problem could you let me know which tutorial are you talking
about.
Perhaps you can answer a couple of simple question so that I have an idea of
your environment:
-what JVM were you using
- how much heap memory did you allocate for Eclipse to run (I mean did you
specify any -Xmx jvm parameter)
- how many rules did the symptom catalog contain
- did you use a symptom 2.0 or 0.1 catalog and the default log analyser
(i.e. XPath log analyser)
- how many records has the log file

From your description my guess is that you may have been close to the heap
limit, but if the catalog you were analysing against was small then it
shouldn't make too much of a difference.
What you can do is just run Eclipse with let's say the following command
line (assuming you have a jvm in your system path):
eclipse -Xmx512m -Xms40m, open the log file that you were trying to analyse
(I just assume this log file has less then 20000 records) and reanalyse.

"Alessandro Tucci" <intucci@tin.it> wrote in message
news:a42942b42dbb609d84d8c454e6b612bd$1@www.eclipse.org...
> Hi everybody,
> I experienced some trouble using log view and symptom catalogs.
> I'm runnning Eclipse 3.3.0 with TPTP 4.4.0.2 all-in-One on Linux SuSE
10.1.
> I am following the tutorial published on TPTP site, so I am tring to
> analyze the log file generated by the sample application.
> I firstly imported the symptom catalog provided in the zip file, then I
> ran thesample web-app to generate some log messages. After that, I stopped
> the server and terminated the profiler. Then I opened the "Profiling and
> Logging" perspective and entered the "Log Navigator Section": the fresh
> new log and the symptom catalog I had imported were there. Therefore, I
> opened the log file, then I right-clicked on a message and I selected
> "Analyze Selection". The event was correctly analized and each field was
> properly reported. On the other hand, a progress bar labeled "Analyzing"
> appeared at the bottom of the window, on the right side: it is a 3-ticks
> bar, but it kept stuck on the first tick. I opened the system performance
> monitor and I found that Eclipse was using 90% of CPU time: the refresh of
> Eclipse UI was really slow (half a minute to repaint the UI). I had been
> waiting for a minute hoping something might change, but: CPU usage was
> always between 80 and 90 percent; the progress bar was still labeled
> "Analyzing" and was still on the first tick; no useful
> information/solution came from the symptom catalog (it should have
> appeared "Do not let Harm put code on your project").
> It seems that nobody else experienced something like that: I couldn't find
> anything similar on google and on this mailing list. Maybe it is an error
> of mine, but I cannot sincerely imagine what could go wrong in following
> few easy steps.
>
> Hoping not to having bothered you with useless doubts,
> I thank you for your attention.
> Alessandro
>
Re: Log view - Analyze selection: 90% CPU usage [message #108001 is a reply to message #107925] Wed, 08 August 2007 18:28 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Alex,
thanks for your interest.

> I am sorry to hear that you had trouble running a TPTP tutorial, in order to
> understand you problem could you let me know which tutorial are you talking
> about.

I am following this tutorial:
http://www.eclipse.org/tptp/home/documents/tutorials/viewlet s/v4.1/EW-LTAandProbes/EW-LTAandProbes/EW-LTAandProbes_viewl et_swf.html
It is a bit out of date, but it is not hard to translate the steps shown
there to the new UI. :-)
This is the code/documents it deals with:
http://www.eclipse.org/tptp/home/documents/tutorials/viewlet s/v4.4/sample.zip
some references to eclipse plugins have to be corrected to the proper
version of the plugin.

>what JVM were you using
I was/am using JDK 1.5.0 Update 12, the newest among 1.5 JVM's.

>how much heap memory did you allocate for Eclipse to run (I mean did you
>specify any -Xmx jvm parameter)
I do not add any additional parameter to eclipse launch command (in other
words, just type ./eclipse)

>how many rules did the symptom catalog contain
As you will see, the catalogue contains just 1 rule! :-)

>did you use a symptom 2.0 or 0.1 catalog and the default log analyser
>(i.e. XPath log analyser)
The UI provides only the Symptom V2 and IBM format importer, therefore I
chose the first one. Furthermore, I use XPathLogAnalyzer: I could not do
other way, because the other one provided is SymptomV0.1LogAnalyzer.

>how many records has the log file
I tried to generate a log and to analyze an event more than once: log
files had between six and twelve lines, depending on how many times I
clicked on the links in the sample main page. (the tutorial contains a web
app consisting of a main page and three servlets, accessible from three
links on that page. One of this servlet (ShadowedServlet) generates log
events in CBE format)

In the last article I forgot to point out that I tried to close in a clean
way the program (i.e. no SIGKILL, no SIGTERM): it took 10 minutes, without
any other program could significatively interfere with its CPU usage.

As you can see, I am working with a really small amount of data, that is
what is worrying.

I then tried to launch as you suggested:
eclipse -Xmx512m -Xms40m
and reanalyzed.
The behaviour was the same:
- no solutions found (it should be "Do not let harm put code in your
project");
- clicking on show desktop and reclicking on eclipse tab caused a
24-second refresh;
- when I tried to close eclipse in a clean way, I had to wait about 30
seconds to see the confirmation window. After clicking OK, I had been
waiting for 15 minutes (!!) but the process was still alive. The process
table showed that eclipse was still using 90% of CPU time and it was
occupying 530.000 kB of virtual memory. In the meantime, java process was
using 0,00% of CPU time and was occupying about 303.000 kB of virtual
memory.

I launched eclipse from the console, so the output was:
atx85@atx85:~/Programmi/Java/IDE/eclipse_mant/eclipse> ./eclipse -Xmx512m
-Xms40m
newInput = 0
_input = 0

In the end, I killed eclipse, after 20 minutes of useless waiting.

I hope I gave you enough information. If I did not, do not hesitate to ask
for more, I will be glad to help you in helping me! :-)
Thanks for your attention,
Alessandro Tucci
Re: Log view - Analyze selection: 90% CPU usage [message #108102 is a reply to message #108001] Thu, 09 August 2007 04:10 Go to previous messageGo to next message
Alex Nan is currently offline Alex Nan
Messages: 29
Registered: July 2009
Junior Member
Hi Alessandro,

I tried the scenario but on Windows and I had no problem running analysis.
There is though a problem with the recommendations that are not showing up
in the symptom analysis results view. Although the XML in the tutorial zip
is correct, the generic symptom effects are not displayed in the symptom
analysis results view. The symptom effects are just containers for either
recommendations or actions. You would need to add recommendation child
elements to each <symptom:symptomEffect>. Here is how the correct symptom
effect elements would look like:

<symptom:symptomEffect>

<definition>#//@symptomCatalog/@symptomDefinition.0</definition >

<recommendation:recommendation>

<message>Do not every let Harm put code in your project.</message>

</recommendation:recommendation>

</symptom:symptomEffect>

<symptom:symptomEffect>

<definition>#//@symptomCatalog/@symptomDefinition.0</definition >

<recommendation:recommendation>

<message>In case you did not notice, do not let Harm touch your
code</message>

</recommendation:recommendation>

</symptom:symptomEffect>

I am gonna try on Linux Suse and let you know. The problem you are
describing is a bit strange, but we have to track it down, it's something I
have only encountered when large logs against large symptom catalogs are
analysed.

Kind regards,

Alex Nan.

"Alessandro Tucci" <intucci@tin.it> wrote in message
news:cd2c9cff61c0d815510c05195103cfbf$1@www.eclipse.org...
> Hi Alex,
> thanks for your interest.
>
> > I am sorry to hear that you had trouble running a TPTP tutorial, in
order to
> > understand you problem could you let me know which tutorial are you
talking
> > about.
>
> I am following this tutorial:
>
http://www.eclipse.org/tptp/home/documents/tutorials/viewlet s/v4.1/EW-LTAandProbes/EW-LTAandProbes/EW-LTAandProbes_viewl et_swf.html
> It is a bit out of date, but it is not hard to translate the steps shown
> there to the new UI. :-)
> This is the code/documents it deals with:
>
http://www.eclipse.org/tptp/home/documents/tutorials/viewlet s/v4.4/sample.zip
> some references to eclipse plugins have to be corrected to the proper
> version of the plugin.
>
> >what JVM were you using
> I was/am using JDK 1.5.0 Update 12, the newest among 1.5 JVM's.
>
> >how much heap memory did you allocate for Eclipse to run (I mean did you
> >specify any -Xmx jvm parameter)
> I do not add any additional parameter to eclipse launch command (in other
> words, just type ./eclipse)
>
> >how many rules did the symptom catalog contain
> As you will see, the catalogue contains just 1 rule! :-)
>
> >did you use a symptom 2.0 or 0.1 catalog and the default log analyser
> >(i.e. XPath log analyser)
> The UI provides only the Symptom V2 and IBM format importer, therefore I
> chose the first one. Furthermore, I use XPathLogAnalyzer: I could not do
> other way, because the other one provided is SymptomV0.1LogAnalyzer.
>
> >how many records has the log file
> I tried to generate a log and to analyze an event more than once: log
> files had between six and twelve lines, depending on how many times I
> clicked on the links in the sample main page. (the tutorial contains a web
> app consisting of a main page and three servlets, accessible from three
> links on that page. One of this servlet (ShadowedServlet) generates log
> events in CBE format)
>
> In the last article I forgot to point out that I tried to close in a clean
> way the program (i.e. no SIGKILL, no SIGTERM): it took 10 minutes, without
> any other program could significatively interfere with its CPU usage.
>
> As you can see, I am working with a really small amount of data, that is
> what is worrying.
>
> I then tried to launch as you suggested:
> eclipse -Xmx512m -Xms40m
> and reanalyzed.
> The behaviour was the same:
> - no solutions found (it should be "Do not let harm put code in your
> project");
> - clicking on show desktop and reclicking on eclipse tab caused a
> 24-second refresh;
> - when I tried to close eclipse in a clean way, I had to wait about 30
> seconds to see the confirmation window. After clicking OK, I had been
> waiting for 15 minutes (!!) but the process was still alive. The process
> table showed that eclipse was still using 90% of CPU time and it was
> occupying 530.000 kB of virtual memory. In the meantime, java process was
> using 0,00% of CPU time and was occupying about 303.000 kB of virtual
> memory.
>
> I launched eclipse from the console, so the output was:
> atx85@atx85:~/Programmi/Java/IDE/eclipse_mant/eclipse> ./eclipse -Xmx512m
> -Xms40m
> newInput = 0
> _input = 0
>
> In the end, I killed eclipse, after 20 minutes of useless waiting.
>
> I hope I gave you enough information. If I did not, do not hesitate to ask
> for more, I will be glad to help you in helping me! :-)
> Thanks for your attention,
> Alessandro Tucci
>
Re: Log view - Analyze selection: 90% CPU usage [message #108200 is a reply to message #108102] Thu, 09 August 2007 12:25 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Alex,
I would like to point out something about the problem I am experiencing.
I modified the SymptomDatabase file as you suggested. The symptomEffect
tags are in the last part of the file: I added there those two
recommendation tags you provided to me and now it looks like this:

> <?xml version="1.0" encoding="UTF-8"?>
> <symptom:symptomCatalog
xmlns:expression="http://www.eclipse.org/tptp/xpathExpression"
xmlns:symptom="http://www.eclipse.org/tptp/symptom">
> <name>EclipseWorld symptoms</name>
> <description>
> <message>A set of symptom patterns for the EclipseWorld
sessions.</message>
> </description>
> <url></url>
> <symptom:symptomDefinition>
> <name>a good practice symptom</name>
> <description>
> <message>a good practice symptom</message>
> </description>
> <rule>#//@symptomCatalog/@symptomRule.0</rule>
> <effect>#//@symptomCatalog/@symptomEffect.0</effect>
> <effect>#//@symptomCatalog/@symptomEffect.1</effect>
> </symptom:symptomDefinition>
> <symptom:symptomRule>
> <description>
> <message>Harm</message>
> </description>
> <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> <expression:xpathExpression>/CommonBaseEvent[contains(@msg,
>'Harm')]</expression:xpathExpression>
> </symptom:symptomRule>
> <symptom:symptomEffect>
> <description>
> <message>Do not every let Harm put code in your project.</message>
> </description>
> <recommendation:recommendation>
> <message>Do not every let Harm put code in your project.</message>
> </recommendation:recommendation>
> <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> </symptom:symptomEffect>
> <symptom:symptomEffect>
> <description>
> <message>In case you did not notice, do not let Harm touch your
code</message>
> </description>
> <recommendation:recommendation>
> <message>In case you did not notice, do not let Harm touch your
code</message>
> </recommendation:recommendation>
> <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> </symptom:symptomEffect>
> </symptom:symptomCatalog>

Therefore, I deleted the old catalog from the workbench and I imported
this one. I opened "Details" tag and no text field labeled
"Recommendation" appeared. I started surfing amongst the tags looking for
a possible location of that text field, but the UI was becoming gradually
slower. I opened the process table and I saw that eclipse was using 70 -
80 % of User CPU time. I had been waiting for a minute, but nothing
changed: in the meantime, I was experiencing the usual slow refresh. This
time I was less patient and I killed eclipse after about two minutes.
Therefore, it seems that the problem is in the access to the catalog. In
the past articles, I didn't distinguish analyzing from importing because
those two actions were too close to understand which one could be the
cause. Now I can be sure enough about the fact that the mere importing of
the catalogue causes such a CPU abuse.

I hope I have been detailed and helpful,
thanks for your patience and for your interest.
Alessandro
Re: Log view - Analyze selection: 90% CPU usage [message #108213 is a reply to message #108200] Thu, 09 August 2007 14:31 Go to previous messageGo to next message
Alex Nan is currently offline Alex Nan
Messages: 29
Registered: July 2009
Junior Member
Hi Alessandro,

I think I now know what is causing you the problems, I don't know the root
cause but at least we have isolated it, and it appears to be the compiling
of XPath rules, the operation that is common to analysis and import symptom
catalog. Actually I would need to ask you first which TPTP build are you
using, I assume it's a 4.4?
In order for the recommendations to be resolved when loading the catalog in
memory you need to change the header and add
the recommendation namespace. Here is the correct XML header for the catalog
that you have sent me.

<?xml version="1.0" encoding="UTF-8"?>
<symptom:symptomCatalog
xmlns:expression="http://www.eclipse.org/tptp/xpathExpression"
xmlns:recommendation="http://www.eclipse.org/tptp/symptom/recommendation"
xmlns:symptom="http://www.eclipse.org/tptp/symptom">

I would say open a defect against TPTP and I'm gonna attach a jar that I
would like you to test to make sure it's the compiling that is the problem.
The jar will also get you going.
Thank you,
Alex Nan.


"Alessandro Tucci" <intucci@tin.it> wrote in message
news:57c86b029fb5c5ebc29060415b90946a$1@www.eclipse.org...
> Hi Alex,
> I would like to point out something about the problem I am experiencing.
> I modified the SymptomDatabase file as you suggested. The symptomEffect
> tags are in the last part of the file: I added there those two
> recommendation tags you provided to me and now it looks like this:
>
> > <?xml version="1.0" encoding="UTF-8"?>
> > <symptom:symptomCatalog
> xmlns:expression="http://www.eclipse.org/tptp/xpathExpression"
> xmlns:symptom="http://www.eclipse.org/tptp/symptom">
> > <name>EclipseWorld symptoms</name>
> > <description>
> > <message>A set of symptom patterns for the EclipseWorld
> sessions.</message>
> > </description>
> > <url></url>
> > <symptom:symptomDefinition>
> > <name>a good practice symptom</name>
> > <description>
> > <message>a good practice symptom</message>
> > </description>
> > <rule>#//@symptomCatalog/@symptomRule.0</rule>
> > <effect>#//@symptomCatalog/@symptomEffect.0</effect>
> > <effect>#//@symptomCatalog/@symptomEffect.1</effect>
> > </symptom:symptomDefinition>
> > <symptom:symptomRule>
> > <description>
> > <message>Harm</message>
> > </description>
> > <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> > <expression:xpathExpression>/CommonBaseEvent[contains(@msg,
> >'Harm')]</expression:xpathExpression>
> > </symptom:symptomRule>
> > <symptom:symptomEffect>
> > <description>
> > <message>Do not every let Harm put code in your project.</message>
> > </description>
> > <recommendation:recommendation>
> > <message>Do not every let Harm put code in your project.</message>
> > </recommendation:recommendation>
> > <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> > </symptom:symptomEffect>
> > <symptom:symptomEffect>
> > <description>
> > <message>In case you did not notice, do not let Harm touch your
> code</message>
> > </description>
> > <recommendation:recommendation>
> > <message>In case you did not notice, do not let Harm touch your
> code</message>
> > </recommendation:recommendation>
> > <definition>#//@symptomCatalog/@symptomDefinition.0</definition >
> > </symptom:symptomEffect>
> > </symptom:symptomCatalog>
>
> Therefore, I deleted the old catalog from the workbench and I imported
> this one. I opened "Details" tag and no text field labeled
> "Recommendation" appeared. I started surfing amongst the tags looking for
> a possible location of that text field, but the UI was becoming gradually
> slower. I opened the process table and I saw that eclipse was using 70 -
> 80 % of User CPU time. I had been waiting for a minute, but nothing
> changed: in the meantime, I was experiencing the usual slow refresh. This
> time I was less patient and I killed eclipse after about two minutes.
> Therefore, it seems that the problem is in the access to the catalog. In
> the past articles, I didn't distinguish analyzing from importing because
> those two actions were too close to understand which one could be the
> cause. Now I can be sure enough about the fact that the mere importing of
> the catalogue causes such a CPU abuse.
>
> I hope I have been detailed and helpful,
> thanks for your patience and for your interest.
> Alessandro
>
Re: Log view - Analyze selection: 90% CPU usage [message #108224 is a reply to message #108213] Thu, 09 August 2007 17:48 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Alex,
I am using TPTP Maintenance 4.4.0.2 built on 27th July 2007.
I changed the header just as you suggested to me and I surprisingly did
not experience any problem during the importing of the catalogue:
furthermore, I can find the "Recommendation" text field in the "Details"
tab now. No hope about log analysis, instead: CPU abuse and no
recommendation shown. I noticed that it can be read "Symptom Analysis
Results (Page 1 of 0 Filter matched 0 of 0 records" above the table
contained in "Symptom Analysis Result View" tab.
Just a question about opening a defect. I have absolutely no experience
about professional software development, therefore I did not understand:
- whether I have to open that defect or you are going to do it;
- where I will be able to download the jar you mentioned (on the bug page,
I suppose, but please give me a confirmation :-) ).

Thanks for your patience and your interest,
Alessandro



Alex Nan wrote:

> Hi Alessandro,

> I think I now know what is causing you the problems, I don't know the root
> cause but at least we have isolated it, and it appears to be the compiling
> of XPath rules, the operation that is common to analysis and import symptom
> catalog. Actually I would need to ask you first which TPTP build are you
> using, I assume it's a 4.4?
> In order for the recommendations to be resolved when loading the catalog in
> memory you need to change the header and add
> the recommendation namespace. Here is the correct XML header for the catalog
> that you have sent me.

> <?xml version="1.0" encoding="UTF-8"?>
> <symptom:symptomCatalog
> xmlns:expression="http://www.eclipse.org/tptp/xpathExpression"
> xmlns:recommendation="http://www.eclipse.org/tptp/symptom/recommendation"
> xmlns:symptom="http://www.eclipse.org/tptp/symptom">

> I would say open a defect against TPTP and I'm gonna attach a jar that I
> would like you to test to make sure it's the compiling that is the problem.
> The jar will also get you going.
> Thank you,
> Alex Nan.
Re: Log view - Analyze selection: 90% CPU usage [message #108264 is a reply to message #108224] Thu, 09 August 2007 22:50 Go to previous messageGo to next message
Alex Nan is currently offline Alex Nan
Messages: 29
Registered: July 2009
Junior Member
Hi Alessandro,

no problem, I can provide you guidance on how to open a defect:
follow the link https://bugs.eclipse.org/bugs/enter_bug_wizard.cgi
you need to register first (just provide an e-mail address) and then log in
and follow the link
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=TPTP%20L og%20Analyzer
select Platform.UI.LogView as the component name, 4.4.0.2 as the version
and the operating system, describe the problem and click submit.
I am gonna attach a jar to the defect that you can use to test.
Kind regards,
Alex Nan.

"Alessandro Tucci" <intucci@tin.it> wrote in message
news:e92f6d295eeaf7539b4d1a89cea3ebf7$1@www.eclipse.org...
> Hi Alex,
> I am using TPTP Maintenance 4.4.0.2 built on 27th July 2007.
> I changed the header just as you suggested to me and I surprisingly did
> not experience any problem during the importing of the catalogue:
> furthermore, I can find the "Recommendation" text field in the "Details"
> tab now. No hope about log analysis, instead: CPU abuse and no
> recommendation shown. I noticed that it can be read "Symptom Analysis
> Results (Page 1 of 0 Filter matched 0 of 0 records" above the table
> contained in "Symptom Analysis Result View" tab.
> Just a question about opening a defect. I have absolutely no experience
> about professional software development, therefore I did not understand:
> - whether I have to open that defect or you are going to do it;
> - where I will be able to download the jar you mentioned (on the bug page,
> I suppose, but please give me a confirmation :-) ).
>
> Thanks for your patience and your interest,
> Alessandro
>
>
>
> Alex Nan wrote:
>
> > Hi Alessandro,
>
> > I think I now know what is causing you the problems, I don't know the
root
> > cause but at least we have isolated it, and it appears to be the
compiling
> > of XPath rules, the operation that is common to analysis and import
symptom
> > catalog. Actually I would need to ask you first which TPTP build are you
> > using, I assume it's a 4.4?
> > In order for the recommendations to be resolved when loading the catalog
in
> > memory you need to change the header and add
> > the recommendation namespace. Here is the correct XML header for the
catalog
> > that you have sent me.
>
> > <?xml version="1.0" encoding="UTF-8"?>
> > <symptom:symptomCatalog
> > xmlns:expression="http://www.eclipse.org/tptp/xpathExpression"
> >
xmlns:recommendation="http://www.eclipse.org/tptp/symptom/recommendation"
> > xmlns:symptom="http://www.eclipse.org/tptp/symptom">
>
> > I would say open a defect against TPTP and I'm gonna attach a jar that I
> > would like you to test to make sure it's the compiling that is the
problem.
> > The jar will also get you going.
> > Thank you,
> > Alex Nan.
>
Re: Log view - Analyze selection: 90% CPU usage [message #108303 is a reply to message #108264] Fri, 10 August 2007 11:18 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Alex,
with immense emotion and awe I opened my first bug! :-)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=199547
Please, report me any error, neglectance or unopportune section you can
find in that page, it will be useful for the next time I do it.
Thanks for your guidance and for your patience.
Alessandro Tucci
Re: Log view - Analyze selection: 90% CPU usage [message #108448 is a reply to message #108303] Fri, 10 August 2007 18:45 Go to previous message
Alex Nan is currently offline Alex Nan
Messages: 29
Registered: July 2009
Junior Member
Thank you Alessandro, the defect you opened contains all the neccesary
information. We're gonna comunicate through bugzilla, I will attach a jar
file and instructions how to use it.
Alex Nan.

"Alessandro Tucci" <intucci@tin.it> wrote in message
news:95b91dbad9f15b25dc888ae53b082fb5$1@www.eclipse.org...
> Hi Alex,
> with immense emotion and awe I opened my first bug! :-)
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=199547
> Please, report me any error, neglectance or unopportune section you can
> find in that page, it will be useful for the next time I do it.
> Thanks for your guidance and for your patience.
> Alessandro Tucci
>
Previous Topic:TPTP contributes invalid menu extension with 3.3
Next Topic:TPTP 4.4 failure
Goto Forum:
  


Current Time: Thu Sep 18 15:56:43 GMT 2014

Powered by FUDForum. Page generated in 0.32905 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software