So this ticket was originally intended to (at least) figure out how to fix the (presumed) pdb bug that was preventing the stack traces from printing, but after I investigated for a bit, it didn't look like there was a pdb bug. My search for other culprits didn't hit the mark, but then we think Austin probably found the cause: https://bugs.openjdk.org/browse/JDK-8273392 Assuming that's right, and perhaps even as a test to see if it's right, we thought one possible approach would be to turn that option off at one of the sites and see if the stack traces appear. That would also (more importantly in the short term) hopefully allow us to see what's causing the command failures. We think we should be able to disable the optimization, which should restore the stack traces by adding this JVM argument to the pdb invocation: -XX:-OmitStackTraceInFastThrow |