Bug 188264

Summary: Exception during execution
Product: [Fedora] Fedora Reporter: Mladen Adamovic <adamm>
Component: eclipseAssignee: Ben Konrath <ben>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-08 06:14:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mladen Adamovic 2006-04-07 15:06:09 UTC
Description of problem:
If exception occur during execution of the Java program inside FC5 Eclipse 3.1.2
(i.e. NullPointException) Eclipse print the HREF and that is normal. This HREF
is clickable and that is still OK. The bug is that if I click to this HREF Eclipse 

Version-Release number of selected component (if applicable):


How reproducible:
With something like the following (FC5 is on my other computer so please correct
syntax error if any).
import java.io.*;
public class foo {
  public static void main(String[] args) {
    String s;
    system.out.println(s.length());
}
}

Steps to Reproduce:
1. Run the program above 
2. Click in the Console output the location of the error
3.
  
Actual results:
Internal Eclipse error

Expected results:
Position inside the file

Additional info:

Comment 1 Ben Konrath 2006-04-08 04:25:19 UTC
Are you seeing behaviour similar to bug #183212? Or is it something different?

Comment 2 Mladen Adamovic 2006-04-08 06:12:57 UTC
Yes, this bug is duplicate of <a
href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183212" bug
#183212</a>. And there is this bug even better explained. Sorry for bothering you.


Comment 3 Mladen Adamovic 2006-04-08 06:14:28 UTC

*** This bug has been marked as a duplicate of 183212 ***

Comment 4 Ben Konrath 2006-04-08 16:47:11 UTC
It's no bother. Thanks for filing the bug :)