[
https://issues.jboss.org/browse/JBIDE-8548?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-8548:
--------------------------------------
The command ("org.jboss.tools.remote.debug.ui5951") is
undefined
The command ("org.jboss.tools.remote.debug.ui.configure") is undefined
Will fix it. Commands have to be defined if we want to add key bindings (CTRL-1 ..., for
instance). I think key bindings don't mean to much in this case because they have to
be defined dynamically and the user can't know what key binding is associated with
some application. However if you think key bindings would be usable here, I will add
them.
disconnect debug
select project 2 - remote debug
select project 2 - configure
"default" remote debug launch is still associated with
project 1
This is a bug. Will fix it ASAP. I will also add the following functionality:
- when the user selects both of the projects (or more than two projects), all the selected
projects will be included in the source attachment.
Caused by: sun.jvmstat.monitor.MonitorException: Could not
synchronize with target
I have noticed that problem. It happens when the application is started with the
"suspend=y" option and no debug session is attached.
The MonitoredVmUtil.jvmArgs and MonitoredVmUtil.isAttachable methods throw this exception
(you can also check this using your snippet). JConsole shows only PID for such
applications and it isn't possible to connect to them. We can skip the isAttachable
method, but we can't find any port without the jvmArgs method. It seems we can't
discover a suspended application this way.
I will try to find a solution for this issue. Since we can find PID of an application, I
will try to find a port that is opened by the application. I think this can be performed
using netstat on Linux and Windows and lsof on Mac OS X.
Support auto discovery of remote processes for debugging
--------------------------------------------------------
Key: JBIDE-8548
URL:
https://issues.jboss.org/browse/JBIDE-8548
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Fix For: 3.3.0.M3, 3.3.x
Attachments: 8548-1.png, 8548-2.png, 8548-3.png,
org.jboss.tools.remote.debug.zip
It would be helpful if Eclipse could provide a 'debug as' with auto discover of
local java processes, somewhat like jconsole does. Eclipse should also auto associate the
debug session with the current project.
'debug as' -> 'remote process x'
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira