[
https://issues.apache.org/jira/browse/DERBY-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5819:
---------------------------------
Attachment: derby-5819d.diff
Added an other option to control the way the subprocesses are started:
derby.test.debugSuspend=<y|n> default 'y'
Unless this property is 'n', the subprocess will hang till the debugger is
connected, cf the explanation here:
http://docs.oracle.com/javase/1.5.0/docs/guide/jpda/conninv.html#Invocation
> Add logic to BaseTestCase to start subprocesses ready to be attached to from
> a Java debugger
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-5819
> URL: https://issues.apache.org/jira/browse/DERBY-5819
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: derby-5819.diff, derby-5819b.diff, derby-5819c.diff,
> derby-5819d.diff
>
>
> Sometimes it's useful to be able to attach to subprocesses of tests with a
> debugger.
> Now that we have centralized subprocess creation in BaseTestCase#execJavaCmd
> it would be easy and useful to have subprocesses start, but wait for a
> debugger to attach to them, i.e. with these options on an Oracle VM:
> -Xdebug -Xrunjdwp:transport=dt_socket,address=<port>,server=y,suspend=y
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
