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 184197 - Remote debug doesn't work in Sunstudio 12.1
Summary: Remote debug doesn't work in Sunstudio 12.1
Status: NEW
Alias: None
Product: third-party
Classification: Unclassified
Component: DBX-Gui (show other bugs)
Version: -S1S-
Hardware: PC Linux
: P2 normal (vote)
Assignee: ivan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-14 17:46 UTC by kaleva
Modified: 2010-06-10 20:30 UTC (History)
1 user (show)

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 kaleva 2010-04-14 17:46:47 UTC
I've installed Sunstudio 12.1 on both computers (tiger -- workstation and phenom -- build server). dbx and other sunstudio components are in $PATH
Remote program execution works, but remote debug doesn't.

After I have tried to start remote debugging session th following messages about warnings and errors were displayed:

Warning
glue: Surrogate.get_sm(): cannot connect to 'sm' on 'phenom' -- cannot get a beachhead
remote execution exited with 127
rfindsm: null/prod/lib/findsm
sm: null/prod/lib

Error
Connecting to 'remote exec service' (for ELF header info) on phenom failed: 
cannot get to 'sm' -- cannot get a beachhead
remote execution exited with 127
rfindsm: null/prod/lib/findsm
sm: null/prod/lib

Warning
glue: Surrogate.get_sm(): cannot connect to 'sm' on 'phenom' -- cannot get a beachhead
remote execution exited with 127
rfindsm: null/prod/lib/findsm
sm: null/prod/lib

Error
Connecting to 'remote exec service' (for debug engine) on phenom failed: 
cannot get to 'sm' -- cannot get a beachhead
remote execution exited with 127
rfindsm: null/prod/lib/findsm
sm: null/prod/lib

Connecting to dbx failed: null


So remote debug failed
Comment 1 soldatov 2010-06-10 10:53:06 UTC
theoretically remote debugging works in 12.1.
2 hints:
- help from dbxtool:
Debugging on a Remote Host
When you start or configure a debugging session, you can choose to run the dbx debugger on the local host where you are running dbxtool, or on a remote host.
Tcp forwarding must be enabled on both the local host and the remote host. To enable tcp forwarding on each host:
Open the /etc/ssh/sshd_config file and change the setting of the AllowTcpForwarding property to yes.
Restart the ssh daemon /usr/lib/ssh/sshd.
To define a remote host:
Open the Remote Host Settings dialog box by choosing Tools > Hosts, or by clicking Hosts in the Debug Executable dialog box, the Debug Core File dialog box, the Configure Current Debugged Session dialog box, or the Attach dialog box.
Click Duplicate to create a new remote host.
Type the host name in the Host Name field.
Select the platform from the Platform drop-down list.
Make sure that the Studio Location field contains the path to the installation directory for your Sun Studio software; for example, /opt/sunstudio12.1 on Solaris platforms and /opt/sun/sunstudio12.1 on Linux platforms.
The Login Name is automatically set.
Click OK. dbxtool connects to the remote host and the new host is added to the list of hosts.

- path to Sun Studio should be /opt/...../bin
Comment 2 ivan 2010-06-10 20:30:29 UTC
Is this when using the IDE or dbxtool?

The 'null' in the error messages:

rfindsm: null/prod/lib/findsm
sm: null/prod/lib

indicates that the software doesn't know the correct remote location of dbx
(from which it derives the location of rfindsm and sm)

In the 12.1 IDE Please make sure that the ToolCollection list for your intended
remote host has one called SunStudio. (You can access the "ToolCollection" via 
Tools->Options->C/C++->BuildTools.) The "SunStudio" toolchain is usually created
automatically when any SunStudio toolchain is discovered remotely.
The RestoreDefaults button at the bottom of the same panel will re-generate
the list of discovered compilers.