8332917: failure_handler should execute gdb "info threads" command on linux
Reviewed-by: lmesnik, sspitsyn
This commit is contained in:
parent
b3e29db144
commit
ec88c6a872
@ -49,7 +49,7 @@ native.locks.app=lslocks
|
||||
native.locks.args=-u --pid %p
|
||||
|
||||
native.stack.app=gdb
|
||||
native.stack.args=--pid=%p\0-batch\0-ex\0thread apply all backtrace
|
||||
native.stack.args=--pid=%p\0-batch\0-ex\0info threads\0-ex\0thread apply all backtrace
|
||||
native.stack.args.delimiter=\0
|
||||
native.stack.params.repeat=6
|
||||
|
||||
@ -63,7 +63,7 @@ native.core.timeout=600000
|
||||
cores=native.gdb
|
||||
native.gdb.app=gdb
|
||||
# Assume that java standard laucher has been used
|
||||
native.gdb.args=%java\0-c\0%p\0-batch\0-ex\0thread apply all backtrace
|
||||
native.gdb.args=%java\0-c\0%p\0-batch\0-ex\0info threads\0-ex\0thread apply all backtrace
|
||||
native.gdb.args.delimiter=\0
|
||||
|
||||
################################################################################
|
||||
|
Loading…
Reference in New Issue
Block a user