Eclipse Community Forums: Buckminster » Debugging headless Buckminster?

Home » Archived » Buckminster » Debugging headless Buckminster?

Debugging headless Buckminster? [message #754593]

Thu, 03 November 2011 08:58

Eclipse User

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...

Volker

Re: Debugging headless Buckminster? [message #754605 is a reply to message #754593]

Thu, 03 November 2011 09:26

Eclipse User

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

Re: Debugging headless Buckminster? [message #754607 is a reply to message #754605]

Thu, 03 November 2011 09:32

Eclipse User

Silly me, I forget about --displaystacktrace:

...
Waiting for jobs to end
java.lang.NullPointerException
at org.eclipse.buckminster.core.commands.Launch.internalRun(Launch.java:211)
at org.eclipse.buckminster.core.commands.WorkspaceCommand.run(WorkspaceCommand.java:91)
at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(AbstractCommand.java:200)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:317)
at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:136)
at org.eclipse.buckminster.cmdline.Headless.start(Headless.java:156)

Doesn't help me much, so I think I'll try your way next. Thanks!

-Volker

Re: Debugging headless Buckminster? [message #754625 is a reply to message #754605]

Thu, 03 November 2011 12:01

Eclipse User

Hi Thomas,
ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=362814 just in...

The JUnit launch had console output disabled through

<booleanAttribute key="org.eclipse.debug.core.capture_output" value="false"/>

which blew up Buckminster. Removing this line works around the issue.

-Volker

Previous Topic:	Buckminster build does not provide sufficient information to identify missing dependencies
Next Topic:	git.auto.fetch buggy?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 13:31:47 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter