You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2014/03/16 05:57:30 UTC
[jira] [Updated] (SOLR-3291) Update "ant run-example" JVM debugging
command-line switches
[ https://issues.apache.org/jira/browse/SOLR-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-3291:
-------------------------------
Fix Version/s: (was: 4.7)
4.8
> Update "ant run-example" JVM debugging command-line switches
> ------------------------------------------------------------
>
> Key: SOLR-3291
> URL: https://issues.apache.org/jira/browse/SOLR-3291
> Project: Solr
> Issue Type: Improvement
> Reporter: Erik Hatcher
> Fix For: 4.8
>
>
> Our current run-example target uses {code}-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=${example.debug.suspend},address=5005{code}
> but I've heard that it can be done without -X arguments like this
> {code}-agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y{code}
> What's the most up-to-date best way to enable JVM debugging? Are changes warranted?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org