Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Shared target platform, debugging, and multiple dev platforms
Shared target platform, debugging, and multiple dev platforms [message #335038] Wed, 18 March 2009 12:54 Go to next message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

[Sorry for the cross-post, but I'm not sure which audience is most
likely to be able to help]

Our team uses a shared (in CVS) target platform. This target includes
the Eclipse SDK (3.4.1) and a lot of other features/plugins. It includes
the SWT source plugins for both win32 and macosx.
The problem is when debugging on OS X. During coding, navigating the
code for SWT classes works correctly, it uses the macosx source plugin
and displays the OS X specific code. But when debugging, the debugger is
using the win32 source code instead, even though what is executing is
(obviously) the macosx code. It results in the debugger line numbers not
aligning properly with the displayed source files.
The launch configuration we use for launching our app on Mac
specifically excludes all win32 SWT plugins and specifically includes
the macosx SWT source and binary plugins.

So what is the proper way to set up a dev environment that uses a shared
target platform and will debug properly on both Windows and Mac?

Any help appreciated,
Eric
Re: Shared target platform, debugging, and multiple dev platforms [message #335043 is a reply to message #335038] Wed, 18 March 2009 18:00 Go to previous messageGo to next message
Eclipse UserFriend
Eric Rizzo wrote:
> [Sorry for the cross-post, but I'm not sure which audience is most
> likely to be able to help]
>
> Our team uses a shared (in CVS) target platform. This target includes
> the Eclipse SDK (3.4.1) and a lot of other features/plugins. It includes
> the SWT source plugins for both win32 and macosx.
> The problem is when debugging on OS X. During coding, navigating the
> code for SWT classes works correctly, it uses the macosx source plugin
> and displays the OS X specific code. But when debugging, the debugger is
> using the win32 source code instead, even though what is executing is
> (obviously) the macosx code. It results in the debugger line numbers not
> aligning properly with the displayed source files.
> The launch configuration we use for launching our app on Mac
> specifically excludes all win32 SWT plugins and specifically includes
> the macosx SWT source and binary plugins.

It looks like you are bit by this issue:

247766: Incorrect editor opened on breakpoint when delta pack is
installed in target
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247766

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
Re: Shared target platform, debugging, and multiple dev platforms [message #335051 is a reply to message #335043] Thu, 19 March 2009 10:58 Go to previous message
Eclipse UserFriend
Originally posted by: eclipse-news.rizzoweb.com

On 3/18/2009 6:00 PM, Chris Aniszczyk wrote:
> Eric Rizzo wrote:
>> Our team uses a shared (in CVS) target platform. This target includes
>> the Eclipse SDK (3.4.1) and a lot of other features/plugins. It
>> includes the SWT source plugins for both win32 and macosx.
>> The problem is when debugging on OS X. During coding, navigating the
>> code for SWT classes works correctly, it uses the macosx source plugin
>> and displays the OS X specific code. But when debugging, the debugger
>> is using the win32 source code instead, even though what is executing
>> is (obviously) the macosx code. It results in the debugger line
>> numbers not aligning properly with the displayed source files.
>> The launch configuration we use for launching our app on Mac
>> specifically excludes all win32 SWT plugins and specifically includes
>> the macosx SWT source and binary plugins.
>
> It looks like you are bit by this issue:
>
> 247766: Incorrect editor opened on breakpoint when delta pack is
> installed in target
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=247766

Yes, Chris, I think that is what we're bumping into. Thanks for the
pointer; I've added some comments about our particular scenario.

Eric
Previous Topic:Annotation for problemMarkers
Next Topic:[Databinding] Display error dialog when validation returned error status
Goto Forum:
  


Current Time: Wed Apr 16 10:46:21 EDT 2025

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

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

Back to the top