Description of problem: I'm trying to install F8T3/x86_64 on a 64bit VM under VMWare Server 1.0.4. AFAICS the installation was pretty-much-strait forward. However, when anaconda was trying to install the last packages, it hanged for hours. Switching back to the text consoles doesn't really shows anything critical (beyond a single syntax warning in Anaconda - see attached) I'm keeping the VM image suspend, so please, if you require additional information please let me ASAP. Host configuration: Fedoa 7, x86_64, 2.6.22.9-91.fc7. 2 x Opteron 275. 4GB RPM. 3 x 250GB SATA. nVidia GF6800GT, nVidia binary drivers. Guest configuration: 2 virtual CPUs. 10GB disk space. 512MB RAM. 2 bridged network devices. 2 host-only network devices. USB support. Sound support.
Created attachment 235331 [details] Anaconda console log
Created attachment 235341 [details] Kernel log
Looks like a python problem judging from the console log file.
Chris, if there was a double free problem in the python GC I'm pretty sure I'd be flooded with bugs ... much more likely is that anaconda is calling some C code that is doing the double free. Can you get glibc to print a backtrace/core-dump like it normally does (post install) on double free?
Even after I hard-wired /usr/bin/ls to /bin/ls and /usr/bin/sed to /bin/sed (without it pstack aborted on an error) - pstack anaconda_pid returns nothing. Beyond crashing anaconda by sending a kill -SEGV, any idea how I can yank the call stack? - Gilboa
Doing a kill -ABRT is probably the easiest, assuming nothing turns coredumps off with resource limits ... chris what is the usual way to debug this easily?
kill -ABRT doesn't return anything - anaconda just dies with no crash dump. Reverting to last bad-known snapshot. - Gilboa
Have you encountered this problem in Fedora 9?
F9 installed cleanly. Bug can be closed. - Gilboa