|
| Re: Debugging headless Buckminster? [message #754605 is a reply to message #754593] |
Thu, 03 November 2011 13:26   |
|
On 2011-11-03 13:59, Volker Stolz wrote:
> I'm seeing the following with Buckminster 3.7 headless:
>
> bash-3.00$ buckminster --loglevel DEBUG -data `pwd` launch -l ABSFrontend/frontend.launch --stderr --stdout
> launch '-l' 'ABSFrontend/frontend.launch' '--stderr' '--stdout'
> Doing full workspace refresh
> Waiting for jobs to end
> java.lang.NullPointerException
>
> Which knobs do I have to allow me to track this one down? It would be nicer to have the full stacktrace...
>
I agree. Unfortunately we're not in control over all code that throws exceptions. Some code catches them and simply
print the message on System.out.
Buckminster can be debugged from Eclipse. We provide source bundles that you can install. If you want to debug the
headless one, you'll need to set it up for remote execution debugging by passing a JVM argument at startup:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=y
Then create a remote launch configuration in Eclipse. Start Buckminster (it will startup but then wait) and start debugging.
HTH,
- thomas
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03813 seconds
] 
Search
Help
Register
Login
Home
