JDB (attn. squ1d, Sigma)

[Cyborg Girl]

This debugger has no built-in keyboard shortcuts! Or autocompletion! Or command history! Or even, as far as I can tell, means of telling it to repeat a command. Argh!

But anyway: how do I make it show me what *handled* exception caused a program to gracefully exit?

(I'm trying to debug a CLI frontend. For an encryption library. That catches java.lang.Throwable in the main() method of the CLI utility, and is giving me an incredibly vague and unhelpful error message about "bad input." Sigh.)

Edit: somehow I missed <n> <command>. N/M...

[squ1d]

My advice would be unquestionably to use an IDE so you can be efficient. Command line development is really slow and I would avoid it like the plague. I've never used jdb before because of that fact!

With regards to the exception, have you solved that problem?

[Cyborg Girl]

Figured you'd say that about IDEs... I'll try it in Eclipse I guess. Technically this is not even supposed to be my job, but the Java developers all seem to be otherwise occupied...

And no, I haven't solved it yet. Tried to subscribe to the mailing list -> subscription was never processed, email bounced with a message that I should use their new forums. When to where the forums should be -> got a DNS error, it looks like the site doesn't exist any more. The last SVN commit on the project was over 6 months ago.

*bonk bonk bonk*

[Sigma_Orionis]

Never used JBD.

[squ1d]

Full error text? Stack trace?