Context Navigation

Changes between Initial Version and Version 1 of Ticket #12317, comment 7

initial	v1
16	16	- wouldn't it be better if the kernel "held tight" on the crashed thread, instead of letting it go ?
17	17	- if it isn't, how could Debugger give a hint about what happened ? Seeing a list of threads with no indication of any of them being stopped gives the (false) impression that the Debugger report is spurious and the team did not really crash. We probably don't want that.
	18
	19	EDIT: clearly I was using the wrong tool for the job, best rely on the ''syslog'' to have a "snapshot" situation at the time of the crash. As a general example, we sometimes have DJ's coming in the morning and clicking "create report" for a crash that occured during the night, and obviously the situation can have changed during the elapsed several hours. Note to self: the syslog backtrace can be prettyfied with /bin/c++filt