Home » Newcomers » Newcomers » Stack trace dropping point for Eclipse?
| Stack trace dropping point for Eclipse? [message #202939] |
Tue, 03 April 2007 02:18  |
Eclipse User |
|
|
|
Hy,
I was wondering if there exists a site where I could just send in the stack
traces that Eclipse reports.
This would be really nice as sometimes I don't know what caused the problem
(so writing a TR is hopeless), but the stack trace might already contain the
info needed to find the bug
|
|
| |
| Re: Stack trace dropping point for Eclipse? [message #203170 is a reply to message #203015] |
Wed, 04 April 2007 01:05  |
| Eclipse User |
|
|
|
No, I don't really have a stack trace right now.
My problem is that there are many times when Eclipse throws seemingly random
exceptions that (seemingly) does not effect my work. For example if my
network connection goes down, than code completition in Eclipse (started
after the network failure) throws some exceptions, stating that Eclipse
can't reach the network.
I was thinking on way to report such exceptions into a "big bag of
exceptions", and if someone feels like correcting some random bugs he can
take a look into this bag.
This would not be an official Bug report as people like me, might not even
be able to tell what they were doing when the exception was thrown, but the
Exception itself might already be enough to point out some easy to find
problems.
This should just be some "I don't really want to start programming some big
feature, but correcting some minor bugs in a few lines is still ok" kind of
quality increasing something.
BR
Kristof
"Ian Bull" <irbull@cs.uvic.ca> wrote in message
news:euttp6$i4j$2@build.eclipse.org...
> If you have a particular stack trace, you can post it here. Someone may
> be able to help (or at least point you in the right direction).
>
> Do you have any idea what caused the problem (ie were you using Birt, or
> CDT, or any other plug-ins?, or was it something in the core).
>
> cheers,
> ian
>
> Kristof Szabados wrote:
> > Hy,
> >
> > I was wondering if there exists a site where I could just send in the
stack
> > traces that Eclipse reports.
> >
> > This would be really nice as sometimes I don't know what caused the
problem
> > (so writing a TR is hopeless), but the stack trace might already contain
the
> > info needed to find the bug
> >
> >
|
|
| | |
| Re: Stack trace dropping point for Eclipse? [message #203366 is a reply to message #203179] |
Wed, 04 April 2007 13:31 |
| Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
You raise a very good point Kristof.
What should end users do when they see errors on their screen. Ideally,
we are all supposed to create steps to reproduce the problem, with the
latest (milestone) build of Eclipse, and open a bug report with all the
details, but the truth is, this is a lot of work. I don't know of any
way just to send a Stack Trace in, but this is a good idea.
I could imagine that Eclipse.org could store a database of stack traces,
and if two stack traces are the same, they get flagged as such. If the
same stack trace occurs a bunch of times, a bug report could
automatically get created.
I know Denis (The webmaster) reads this newsgroup on occasion. Maybe he
has some thoughts on this issue.
cheers,
ian
Kristof Szabados wrote:
> Now I created such a "code completition fails without network" exception.
>
> Error
> Wed Apr 04 07:09:25 CEST 2007
> Internal Error
>
> Java Model Exception: Java Model Status [Cannot retrieve the attached
> javadoc for ProcessBuilder [in ProcessBuilder.class [in java.lang [in
> C:\Program Files\Java\jre1.5.0_07\lib\rt.jar]]]java.net.ConnectExceptio n:
> Connection timed out: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.net.NetworkClient.doConnect(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.openServer(Unknown Source)
> at sun.net.www.http.HttpClient.<init>(Unknown Source)
> at sun.net.www.http.HttpClient.New(Unknown Source)
> at sun.net.www.http.HttpClient.New(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (Unknown
> Source)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unk nown Source)
> at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(U nknown
> Source)
> at
> org.eclipse.jdt.internal.core.JavaElement.getURLContents(Jav aElement.java:73
> 4)
> at
> org.eclipse.jdt.internal.core.BinaryType.getJavadocContents( BinaryType.java:
> 1086)
> at
> org.eclipse.jdt.internal.core.BinaryMethod.getAttachedJavado c(BinaryMethod.j
> ava:531)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getHTMLCo ntentReader(Prop
> osalInfo.java:112)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.extractJa vadoc(ProposalIn
> fo.java:99)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.computeIn fo(ProposalInfo.
> java:76)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getInfo(P roposalInfo.java
> :59)
> at
> org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletion Proposal.getAddi
> tionalProposalInfo(AbstractJavaCompletionProposal.java:458)
> at
> org.eclipse.jface.text.contentassist.AdditionalInfoControlle r$3.run(Addition
> alInfoController.java:102)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> ]
> at
> org.eclipse.jdt.internal.core.JavaElement.getURLContents(Jav aElement.java:78
> 1)
> at
> org.eclipse.jdt.internal.core.BinaryType.getJavadocContents( BinaryType.java:
> 1086)
> at
> org.eclipse.jdt.internal.core.BinaryMethod.getAttachedJavado c(BinaryMethod.j
> ava:531)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getHTMLCo ntentReader(Prop
> osalInfo.java:112)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.extractJa vadoc(ProposalIn
> fo.java:99)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.computeIn fo(ProposalInfo.
> java:76)
> at
> org.eclipse.jdt.internal.ui.text.java.ProposalInfo.getInfo(P roposalInfo.java
> :59)
> at
> org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletion Proposal.getAddi
> tionalProposalInfo(AbstractJavaCompletionProposal.java:458)
> at
> org.eclipse.jface.text.contentassist.AdditionalInfoControlle r$3.run(Addition
> alInfoController.java:102)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
>
>
> The platform is: win32, Eclipse 3.2.1
>
>
> "Ian Bull" <irbull@cs.uvic.ca> wrote in message
> news:euttp6$i4j$2@build.eclipse.org...
>> If you have a particular stack trace, you can post it here. Someone may
>> be able to help (or at least point you in the right direction).
>>
>> Do you have any idea what caused the problem (ie were you using Birt, or
>> CDT, or any other plug-ins?, or was it something in the core).
>>
>> cheers,
>> ian
>>
>> Kristof Szabados wrote:
>>> Hy,
>>>
>>> I was wondering if there exists a site where I could just send in the
> stack
>>> traces that Eclipse reports.
>>>
>>> This would be really nice as sometimes I don't know what caused the
> problem
>>> (so writing a TR is hopeless), but the stack trace might already contain
> the
>>> info needed to find the bug
>>>
>>>
>
>
|
|
|
| Re: Stack trace dropping point for Eclipse? [message #203796 is a reply to message #203366] |
Fri, 06 April 2007 13:13 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Ian Bull wrote:
> You raise a very good point Kristof.
>
> What should end users do when they see errors on their screen. Ideally,
> we are all supposed to create steps to reproduce the problem, with the
> latest (milestone) build of Eclipse, and open a bug report with all the
> details, but the truth is, this is a lot of work. I don't know of any
> way just to send a Stack Trace in, but this is a good idea.
>
> I could imagine that Eclipse.org could store a database of stack traces,
> and if two stack traces are the same, they get flagged as such. If the
> same stack trace occurs a bunch of times, a bug report could
> automatically get created.
But a stack trace without the context of what the user was doing at the
time is almost always insufficient. Such a database would fill up with
lots of:
a) false positives, like the one posted in this thread, that are simply
logging of a condition that can't be resolved automatically.
b) useless entries that have no context and thus can't be debugged.
I really don't see any way it could serve any useful purpose without the
people providing the context, in which case we already have Bugzilla.
My $0.02,
Eric
|
|
|
Goto Forum:
Current Time: Sat Jun 28 23:21:24 EDT 2025
Powered by FUDForum. Page generated in 0.10215 seconds |
Home