Thread dump during build with ctrl-\
erik.joelsson at oracle.com
Wed Feb 5 09:15:47 UTC 2014
This is likely caused by the logger shell scrip wrapper that we use to
catch the build output to a file. You can disable logging with
LOG=nofile, maybe that will make signals reach the java process.
On 2014-02-05 06:55, Mike Duigou wrote:
> Hello all;
> I've noticed that I can't seem to use ctrl-\ to get a stack dump of long running java processes (mostly the jdk javac compile) using the new build. Instead I get something like:
> make: *** [jdk-only] Quit (core dumped)
> mike at samuel:~/code/jdk/jdk9-dev$ ./jdk9-dev/common/bin/logger.sh: line 44: 44468 Quit (core dumped) ( exec 3>&1; ( "$@" 2>&1 1>&3; echo $? > "$RCDIR/rc" ) | tee -a $LOGFILE 1>&2; exec 3>&- )
> 44469 (core dumped) | tee -a $LOGFILE
> cat: /tmp/jdk-build-logger.tmp.LiOGwf/rc: No such file or directory
> I can use jps from another shell just fine. Is this behaviour expected? At minimum it looks like the cleanup is incomplete.
More information about the build-dev