Home » Eclipse Projects » Eclipse Platform » [JDT] wrong source editor opened during debugging
| [JDT] wrong source editor opened during debugging [message #326764] |
Mon, 31 March 2008 21:40  |
Eclipse User |
|
|
|
I am developing on windows against a target platform that includes the
delta pack (both 3.4M5). When I open a SWT class (like Widget) using
Ctrl+Shift+T, I see the win32 version (the editor title is Widget.class
and if I link with the package explorer I see it under the win32 fragment).
If I put a breakpoint in this editor, the debugger will stop at the
correct point. However, it will open the gtk source file which does not
correspond to the running code (the green highlight is on the line
number from the win32 source file). Additionally, the editor title is
Widget.java and it does not link to any file in my workspace.
Is this a bug? Or is there a way for me to change it?
Thanks in advance,
Will
|
|
| |
| Re: [JDT] wrong source editor opened during debugging [message #326947 is a reply to message #326902] |
Thu, 03 April 2008 10:19  |
| Eclipse User |
|
|
|
Thanks for the response. No, I do not have any swt fragments other than
the win32 one selected in the plugins tab. Also, under the Preferences
Page for Target Platform, I verified that the target environment is
win32, win32, x86.
However, I do notice that in the Preferences Page for Target Platform,
under Source Code Locations, all the fragment source bundles are listed.
This makes sense because they are all in the target, but maybe the
debugger is choosing one at random?
-Will
Darin Swanson wrote:
> Do you have the swt linux fragment included in the plugins to launch with on
> the Plug-ins tab of your launch configuration?
>
> HTH
> Darins
> http://runnerwhocodes.blogspot.com
>
> "Will Horn" <will.horn@gmail.com> wrote in message
> news:fss3r1$d8n$1@build.eclipse.org...
>> I am developing on windows against a target platform that includes the
>> delta pack (both 3.4M5). When I open a SWT class (like Widget) using
>> Ctrl+Shift+T, I see the win32 version (the editor title is Widget.class and
>> if I link with the package explorer I see it under the win32 fragment).
>>
>> If I put a breakpoint in this editor, the debugger will stop at the
>> correct point. However, it will open the gtk source file which does not
>> correspond to the running code (the green highlight is on the line number
>> from the win32 source file). Additionally, the editor title is
>> Widget.java and it does not link to any file in my workspace.
>>
>> Is this a bug? Or is there a way for me to change it?
>>
>> Thanks in advance,
>> Will
>
>
|
|
|
| Re: [JDT] wrong source editor opened during debugging [message #327609 is a reply to message #326947] |
Fri, 25 April 2008 12:33 |
| Eclipse User |
|
|
|
I realized this issue extends beyond SWT fragments. It happens when I
debug any object in the target. To reproduce it I:
1) Navigate to any object in the target (using Ctrl+Shift+T, Ctrl+click,
etc). This opens the "ClassFileEditor".
2) I put a breakpoint in this editor (I can see the little blue dot).
3) I run the application and it stops at my breakpoint. However, a new
editor is opened, a "CompilationUnitEditor". I do not see my blue
breakpoint dot, I do not have Ctrl+Shift+I inspection*, and in the case
of SWT files, the wrong OS specific file is often opened (which I
described in my first post).
This is on 3.4 M5. I assume I just have something set up incorrectly,
but any help would be greatly appreciated.
-Will
*Ctrl+Shift+I gives this error - "Unable to evaluate the selected
expression: To perform an evaluation, an expression must be compiled in
the context of a Java project's build path. The current execution
context is not associated with a Java project in the workspace."
Will Horn wrote:
> Thanks for the response. No, I do not have any swt fragments other than
> the win32 one selected in the plugins tab. Also, under the Preferences
> Page for Target Platform, I verified that the target environment is
> win32, win32, x86.
>
> However, I do notice that in the Preferences Page for Target Platform,
> under Source Code Locations, all the fragment source bundles are listed.
> This makes sense because they are all in the target, but maybe the
> debugger is choosing one at random?
>
> -Will
>
> Darin Swanson wrote:
>> Do you have the swt linux fragment included in the plugins to launch
>> with on the Plug-ins tab of your launch configuration?
>>
>> HTH
>> Darins
>> http://runnerwhocodes.blogspot.com
>>
>> "Will Horn" <will.horn@gmail.com> wrote in message
>> news:fss3r1$d8n$1@build.eclipse.org...
>>> I am developing on windows against a target platform that includes
>>> the delta pack (both 3.4M5). When I open a SWT class (like Widget)
>>> using Ctrl+Shift+T, I see the win32 version (the editor title is
>>> Widget.class and if I link with the package explorer I see it under
>>> the win32 fragment).
>>>
>>> If I put a breakpoint in this editor, the debugger will stop at the
>>> correct point. However, it will open the gtk source file which does
>>> not correspond to the running code (the green highlight is on the
>>> line number from the win32 source file). Additionally, the editor
>>> title is Widget.java and it does not link to any file in my workspace.
>>>
>>> Is this a bug? Or is there a way for me to change it?
>>>
>>> Thanks in advance,
>>> Will
>>
>>
|
|
|
| Re: [JDT] wrong source editor opened during debugging [message #327616 is a reply to message #327609] |
Fri, 25 April 2008 21:34 |
| Eclipse User |
|
|
|
Cross posting to PDE in case this is a PDE issue.
Will Horn wrote:
> I realized this issue extends beyond SWT fragments. It happens when I
> debug any object in the target. To reproduce it I:
>
> 1) Navigate to any object in the target (using Ctrl+Shift+T, Ctrl+click,
> etc). This opens the "ClassFileEditor".
> 2) I put a breakpoint in this editor (I can see the little blue dot).
> 3) I run the application and it stops at my breakpoint. However, a new
> editor is opened, a "CompilationUnitEditor". I do not see my blue
> breakpoint dot, I do not have Ctrl+Shift+I inspection*, and in the case
> of SWT files, the wrong OS specific file is often opened (which I
> described in my first post).
>
> This is on 3.4 M5. I assume I just have something set up incorrectly,
> but any help would be greatly appreciated.
>
> -Will
>
>
> *Ctrl+Shift+I gives this error - "Unable to evaluate the selected
> expression: To perform an evaluation, an expression must be compiled in
> the context of a Java project's build path. The current execution
> context is not associated with a Java project in the workspace."
>
> Will Horn wrote:
>> Thanks for the response. No, I do not have any swt fragments other
>> than the win32 one selected in the plugins tab. Also, under the
>> Preferences Page for Target Platform, I verified that the target
>> environment is win32, win32, x86.
>>
>> However, I do notice that in the Preferences Page for Target Platform,
>> under Source Code Locations, all the fragment source bundles are
>> listed. This makes sense because they are all in the target, but
>> maybe the debugger is choosing one at random?
>>
>> -Will
>>
>> Darin Swanson wrote:
>>> Do you have the swt linux fragment included in the plugins to launch
>>> with on the Plug-ins tab of your launch configuration?
>>>
>>> HTH
>>> Darins
>>> http://runnerwhocodes.blogspot.com
>>>
>>> "Will Horn" <will.horn@gmail.com> wrote in message
>>> news:fss3r1$d8n$1@build.eclipse.org...
>>>> I am developing on windows against a target platform that includes
>>>> the delta pack (both 3.4M5). When I open a SWT class (like Widget)
>>>> using Ctrl+Shift+T, I see the win32 version (the editor title is
>>>> Widget.class and if I link with the package explorer I see it under
>>>> the win32 fragment).
>>>>
>>>> If I put a breakpoint in this editor, the debugger will stop at the
>>>> correct point. However, it will open the gtk source file which does
>>>> not correspond to the running code (the green highlight is on the
>>>> line number from the win32 source file). Additionally, the editor
>>>> title is Widget.java and it does not link to any file in my workspace.
>>>>
>>>> Is this a bug? Or is there a way for me to change it?
>>>>
>>>> Thanks in advance,
>>>> Will
>>>
>>>
|
|
|
| Re: [JDT] wrong source editor opened during debugging [message #332099 is a reply to message #327616] |
Thu, 02 October 2008 17:28 |
| Eclipse User |
|
|
|
For anyone stumbling upon this later, here's a link to the bug report I
created:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247766
Will Horn wrote:
> Cross posting to PDE in case this is a PDE issue.
>
> Will Horn wrote:
>> I realized this issue extends beyond SWT fragments. It happens when I
>> debug any object in the target. To reproduce it I:
>>
>> 1) Navigate to any object in the target (using Ctrl+Shift+T,
>> Ctrl+click, etc). This opens the "ClassFileEditor".
>> 2) I put a breakpoint in this editor (I can see the little blue dot).
>> 3) I run the application and it stops at my breakpoint. However, a
>> new editor is opened, a "CompilationUnitEditor". I do not see my blue
>> breakpoint dot, I do not have Ctrl+Shift+I inspection*, and in the
>> case of SWT files, the wrong OS specific file is often opened (which I
>> described in my first post).
>>
>> This is on 3.4 M5. I assume I just have something set up incorrectly,
>> but any help would be greatly appreciated.
>>
>> -Will
>>
>>
>> *Ctrl+Shift+I gives this error - "Unable to evaluate the selected
>> expression: To perform an evaluation, an expression must be compiled
>> in the context of a Java project's build path. The current execution
>> context is not associated with a Java project in the workspace."
>>
>> Will Horn wrote:
>>> Thanks for the response. No, I do not have any swt fragments other
>>> than the win32 one selected in the plugins tab. Also, under the
>>> Preferences Page for Target Platform, I verified that the target
>>> environment is win32, win32, x86.
>>>
>>> However, I do notice that in the Preferences Page for Target
>>> Platform, under Source Code Locations, all the fragment source
>>> bundles are listed. This makes sense because they are all in the
>>> target, but maybe the debugger is choosing one at random?
>>>
>>> -Will
>>>
>>> Darin Swanson wrote:
>>>> Do you have the swt linux fragment included in the plugins to launch
>>>> with on the Plug-ins tab of your launch configuration?
>>>>
>>>> HTH
>>>> Darins
>>>> http://runnerwhocodes.blogspot.com
>>>>
>>>> "Will Horn" <will.horn@gmail.com> wrote in message
>>>> news:fss3r1$d8n$1@build.eclipse.org...
>>>>> I am developing on windows against a target platform that includes
>>>>> the delta pack (both 3.4M5). When I open a SWT class (like Widget)
>>>>> using Ctrl+Shift+T, I see the win32 version (the editor title is
>>>>> Widget.class and if I link with the package explorer I see it under
>>>>> the win32 fragment).
>>>>>
>>>>> If I put a breakpoint in this editor, the debugger will stop at the
>>>>> correct point. However, it will open the gtk source file which
>>>>> does not correspond to the running code (the green highlight is on
>>>>> the line number from the win32 source file). Additionally, the
>>>>> editor title is Widget.java and it does not link to any file in my
>>>>> workspace.
>>>>>
>>>>> Is this a bug? Or is there a way for me to change it?
>>>>>
>>>>> Thanks in advance,
>>>>> Will
>>>>
>>>>
|
|
|
Goto Forum:
Current Time: Mon Nov 03 20:53:23 EST 2025
Powered by FUDForum. Page generated in 0.62540 seconds |
Home