Thread dump during build with ctrl-\

[Magnus Ihse Bursie]

I agree, it sounds hairy. A better method might be to find the process with jps and send kill -QUIT to it. 

/Magnus

> On 5 feb 2014, at 07:48, David Holmes <david.holmes at oracle.com> wrote:
> 
> Hi Mike,
> 
>> On 5/02/2014 3:55 PM, 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 don't see how make and all the intervening shells could know to pass the signal through to the JVM process. ??
> 
> David
> 
>> I can use jps from another shell just fine. Is this behaviour expected? At minimum it looks like the cleanup is incomplete.
> 
> 
> 
>> Mike
>> 
>>