Bugzilla – Full Text Bug Listing
| Summary: | unable to lookup java files while debugging | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | John Richardson <john.t.richardson> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
John Richardson
The log entry does not reflect a source lookup problem. Please provide steps to reproduce. When you launch Eclispe, do you use command line options to specify the workspace location? If so, is the location relative or absolute? (In reply to comment #1) > The log entry does not reflect a source lookup problem. Please provide steps > to reproduce. I tried reproducing the problem with a small application also without success. This is a very large application. There are tens of external jars, hundreds of source files, and the debug connection is remote. I can see the files in the editor when opened via the package explorer and via the Open Type dialog (ctrl+shift+t). The sources are in a directory which is linked to on the file system. When the debugger hits a breakpoint, it opens a new editor window which has a title "Filename.methodname() line:88". There is red text in the editor window - "Source not found." If I click on the button in the editor window to change the source lookup, I can get it so the file is displayed when I double click on the stack in the "Debug" window. But I don't get the green bar showing the current debugger position. To answer your questions... The workspace location isn't specified on the command line, it's done in the dialog on startup. It is a full path. What sort of launch configuration are you using to debug your application (for example, "Remote Java Application", "Java Application")? If the launch config has a "Source Lookup" tab, how is it configured? Is a project specified on the launch config (from which the default source lookup path is computed)? If you can get the session to show source without the green bar, it means the editor being opened by the debugger is on a file external to the workspace (does it have a vertical ruler for breakpoints?). (In reply to comment #4) > What sort of launch configuration are you using to debug your application (for > example, "Remote Java Application", "Java Application")? Remote Java Application, socket connection. (with my small testcase, I tried a Remote Java Application as well as a plain Java Application, but neither reproduced the behavior) > If the launch config > has a "Source Lookup" tab, how is it configured? There is a "Source Lookup" tab. It has two paths, one which I configured with the "Edit Source Lookup Path..." button in the editor and the other which is called "Default". "Default" contains a directory with my project and that directory has the sources. If I remove the first path (the path added from the "Edit Source Lookup Path" button) then double clicking on the stack doesn't take me to the editor anymore. > Is a project specified on the > launch config (from which the default source lookup path is computed)? I'm not sure where to find the launch config... > > If you can get the session to show source without the green bar, it means the > editor being opened by the debugger is on a file external to the workspace > (does it have a vertical ruler for breakpoints?). That makes sense. And no, the editor which the debugger brings up does not have the vertical ruler for breakpoints. It does seem weird that this exact project worked in 3.1RC1. Is your project in a symbolic link location? Could this be the same problem as bug 100807? I just got the 3.1 release and it does work for me. Closing. |