On 12/01/2013 11:20 AM, Richard Weinberger wrote:
> 
> I meant xterm for all consoles but con0...
> Such that you can trigger the crash but are still able to see the output.
> 

Not sure if the 2 attached files contains useful info, but here they are:

The back trace of a hanging linux process :
$>sudo gdb /home/tfoerste/devel/linux/linux 27162 -n -batch -ex 'bt full' > bt

and stdout, error and bt of the core file from round #18 of this command :

$> I=0; while [[ : ]]; do ((I=I+1)); echo; echo; echo $I; date; for i in trinity.sh xterm linux port-helper start_uml.sh ; do pkill $i; done; rm -f /mnt/ramdisk/core; start_uml.sh -r ~/virtual/uml/trinity -l /home/tfoerste/devel/linux/linux -y 'con0=fd:0,fd:1 con=xterm' 1>/mnt/ramdisk/$I.out 2>/mnt/ramdisk/$I.err; [[ -f /mnt/ramdisk/core ]] && gdb --core=/mnt/ramdisk/core /home/tfoerste/devel/linux/linux -n -batch -ex 'bt full' > /mnt/ramdisk/$I.bt; sleep 10; done



-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3