Here's another one:

    (bootstrap)root@twb:~# git clone 
git://github.com/lilstevie/CrOS-Hybrid-Kernel.git
    Cloning into CrOS-Hybrid-Kernel...
    *** longjmp causes uninitialized stack frame ***: /usr/bin/qemu-arm-static 
terminated
    ======= Backtrace: =========
    [0x600d6395]
    [0x600d6329]
    [0x600d6293]
    [0x6002ee60]
    [0x6001f2f8]
    [0x600184cd]
    [0x6008e400]
    [0x6037f69d]
    ======= Memory map: ========
    ^C^C^C^C^Z
    [1]+  Stopped                 git clone 
git://github.com/lilstevie/CrOS-Hybrid-Kernel.git
    (bootstrap)root@twb:~# kill -9 %1

    [1]+  Stopped                 git clone 
git://github.com/lilstevie/CrOS-Hybrid-Kernel.git
    (bootstrap)root@twb:~#
    [1]+  Killed                  git clone 
git://github.com/lilstevie/CrOS-Hybrid-Kernel.git
    (bootstrap)root@twb:~# exit
    root@twb:~# qemu-arm-static --version | head -1
    qemu-arm version 0.14.92 (Debian 0.15.0~rc2+dfsg-1), Copyright (c) 
2003-2008 Fabrice Bellard

Because it was on faster hardware, I also tried copying that sid armhf
rootfs onto an Ubuntu Lucid system, with similar results

   root@lucid:~/twb-abuse# chroot squashfs-root/           # NOTE: at this 
point, sid's qemu-arm-static is in the chroot's usr/bin/
   (bootstrap)root@lucid:/# cd root
   (bootstrap)root@lucid:~# export LC_ALL=C
   (bootstrap)root@lucid:~# git clone 
git://github.com/lilstevie/CrOS-Hybrid-Kernel.git
   Cloning into CrOS-Hybrid-Kernel...
   Segmentation fault
   (bootstrap)root@lucid:~# exit
   root@lucid:~/twb-abuse# cp -b /usr/bin/qemu-arm-static 
squashfs-root/usr/bin/    # now it has lucid's qemu
   root@lucid:~/twb-abuse# chroot squashfs-root
   qemu: fatal: cp15 insn ee1d7f70

   R00=4009f958 R01=0d696914 R02=000190e0 R03=00018e00
   R04=42082988 R05=00021106 R06=420829a8 R07=00000000
   R08=00000000 R09=000ae62c R10=4009f000 R11=00000000
   R12=000ae62c R13=4007f450 R14=4008f538 R15=4008b116
   PSR=20000030 --C- T usr32
   ^C^C^C^Z

   # at this point I had to kill -9 the qemu process.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to