This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 144099 - GdbDebugger.getExtension() would fail in remote debugging
Summary: GdbDebugger.getExtension() would fail in remote debugging
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Egor Ushakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-15 16:34 UTC by _ gordonp
Modified: 2009-06-25 10:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gordonp 2008-08-15 16:34:19 UTC
This is due to a change in http://hg.netbeans.org/main/rev/26f7dbe1f5f2 which made the getExtension()
method into a static method and switched from using the platform field to Utilities.getOperatingSystem().
I'm only making it a P4 because (currently) getExtension() is only called for local debugging and
it works for local debugging. But if it were used in remote debugging, it would fail! IMHO, this makes
it a dangerous change because the method could be used in remote development in the future.

The problem is that Utilities.getOperatingSystem() reflects the host the IDE is running on. In the
case of remote development, platform may specify a different PlatformType than U.getOS().

For instance, if you run netbeans on a Mac and remote debug on Solaris, getOS() returns MacOSX and
you get a ".dylib" response from getExtension(). But since the remote host is Solaris, you really
want ".so" (which you'd get with the non-static version of the method).

The difference between platform and Utilities.getOperatingSystem() is subtle. In some cases you do
want the local value, in others you want the remote.
Comment 1 Egor Ushakov 2009-04-29 14:13:37 UTC
fixed some time ago