transcode is giving me a segmentation fault, which I reported as a bug. They now want a backtrace & I've roughly followed http://www.gentoo.org/proj/en/qa/backtraces.xml I used ebuild directly, ending at the install phase, as I don't want to overwrite the live transcode.
I then built a /mnt/debug chroot using roughly http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 (32bit chroot guild for AMD64) with the following binds: mount -o bind /bin /mnt/debug/bin mount -o bind /etc /mnt/debug/etc mount -o bind /dev /mnt/debug/dev mount -o bind /proc /mnt/debug/proc mount -o bind /sys /mnt/debug/sys mount -o bind /tmp /mnt/debug/tmp mount -o bind /home/daiajo /mnt/debug/home/daiajo and moved the /var/tmp/portage/transcode-*/image dirs into /mnt/debug (just usr in this case) The problem comes when trying to chroot into it: # ls /bin/bash /bin/bash # ls /mnt/debug/bin/bash /mnt/debug/bin/bash # chroot /mnt/debug /bin/bash chroot: cannot run command `/bin/bash': No such file or directory Is there a guide for doing this sort of chroot? What is this sort of chroot called? Is there a better way to run a debug transcode without messing with the live system? I googled around but "chroot" hits so many things its hard to find the right one. I also tried running transcode from the image/bin directory with PATH=/var/tmp/portage/transcode-1.0.2-r3/image/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin however tcextract (run in a subshell I believe) is not found. I was going to ask why that didn't work, now I realise the subshells aren't going to see it, doh. I ran tcextract and tcdecode outside of transcode and they worked without complaint, so its the main transcode at fault. Interestingly, transcode still "Segmentation fault"d when tcextract failed to run, so I was able to get my backtrace, just wondering if there is a better way to go about all this. I wouldn't mind having a debug chroot where I could just emerge stuff, like a 32 bit chroot (which I had up and running for a while, removed it because it did not fix my problem, and I was running short of disk space) but I'm not sure how to go about it. -- [email protected] mailing list
