Thanks for the input, all! I ended up solving this particular problem
without the debugger, but I'll have to try this later.
Cheers,
Galen
On Fri, Jan 13, 2017 at 11:49 AM, Galen M O'Sullivan
wrote:
> Hi,
>
> I'm looking at some DUnit tests and wondering if someone can point me in
> the directi
DUnits are automatically run with debugging options on. This means that
each VM started (5 usually, I think - 1 locator and 4 servers) ends up with
a unique ephemeral debug port. Use the options that Kevin pointed out to
set the debug port.
You can just launch your DUnits from IntelliJ too without
+1
On 1/13/17 12:11, Kevin Duling wrote:
These are my notes which Jinmei started me off with:
*Debug GFSH*
*==*
export
JAVA_ARGS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=3
*Debug a DUNIT test*
=
-Ddunit.debug.basePort=2 -Ddunit.debug.
These are my notes which Jinmei started me off with:
*Debug GFSH*
*==*
export
JAVA_ARGS=-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=3
*Debug a DUNIT test*
=
-Ddunit.debug.basePort=2 -Ddunit.debug.suspendVM=1 (-1 means locator,
0-3 means one
Yes, this works. I have done this before. Of course, you need to properly
coordinate between the debugger and the server starting up.
On Fri, Jan 13, 2017 at 11:54 AM, Udo Kohlmeyer
wrote:
> Have you tried starting the remote with
>
> java
> -agentlib:jdwp=transport=dt_socket,address=127.0.0.
Have you tried starting the remote with
java
-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:9001,server=y,suspend=y
–jar application.jar
and then you should be able to have your Idea connect to it using the
"Remote" configuration in your run/debug configurations.
Never tried this...
Hi,
I'm looking at some DUnit tests and wondering if someone can point me in
the direction of the right way to hook a debugger into them. I've been
using IntelliJ to debug in my main development environment, which is a Mac,
but don't have it on the Linux box in which I'm seeing an error. What do
y
