[jbosstools-issues] [JBoss JIRA] (JBIDE-19409) bug in auto-detecting -Xrunjdwp flags in running jvms
[
https://issues.jboss.org/browse/JBIDE-19409?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19409:
-------------------------------------
I would close this issue as no longer relevant. When I first started looking at the code,
I was focussing on this narrow section of parsing the -Xrunjdwp flags, and not actually
running it. The code I committed does accurately fix the section where we parse the
flags, but, it doesn't change the fact that Java requires the transport to be first,
which I was unaware of at the time I 'fixed' it.
So yeah, the patch I made was somewhat useless, but didn't hurt anything.
bug in auto-detecting -Xrunjdwp flags in running jvms
-----------------------------------------------------
Key: JBIDE-19409
URL: https://issues.jboss.org/browse/JBIDE-19409
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.2.3.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.0.Alpha2
Current code in org.jboss.tools.common.jdt.debug.VmModel assumes the debug args start
with -Xrunjdwp:transport when really it can start with
-Xrunjdwp:transport=dt_socket,server=y,address=4000,suspend=n
-Xrunjdwp:address=4000,server=y,transport=dt_socket,suspend=n
-Xrunjdwp:server=y,address=4000,transport=dt_socket,suspend=n
-Xrunjdwp:suspend=n,address=4000,server=y,transport=dt_socket
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)