Hi Ariel,
Ariel Constenla-Haile pisze:
Hi there,
trying OOo 3.1 (Sun's build, OOO310_m11), I find it's impossible (at least on
Linux) to make "Debug Extension in Target OOo". If fails poping up the dialog
with a deffective JRE, asking to choose a new one in the Options dialog.
In NB output window:
ERROR: transport error 202: connect failed: Conexión rehusada
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
JavaVM: JNI_CreateJavaVM called _exit, caught by abort_handler in javavm.cxx
[Java framework] sunjavaplugin.soCan not create JavaVirtualMachine, abort
handler was called.
[Java framework] sunjavaplugin.soCan not create Java Virtual Machine
[Java framework] sunjavaplugin.soCan not create Java Virtual Machine
Of course, with this "Debug Extension in Target OOo" option, a new user dir.
is created on the build dir., which has no Java settings (as it's a brand new
user dir.).
In OOo 3.0.1 everything works.
Any hints?
Hm, I'm not using NB but in Eclipse there's no difference in terms of
debugging the extension in Java between 3.0.1 and 3.1. I was debugging
3.1 just now, so I suppose you must have forgotten to set the the debug
parameters in OOo for your JRE (-Xdebug etc.)
Regards
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
