The workaround presented for this bug is to use taskset. The problem that I have right now is that i am using VMWare. The real physical server have 2 CPUs, but the VMWare guest OS is only configured to use one CPU. This means that I cannot use taskset for setting it against CPU number 1 because the VM thinks that it only have one CPU.
For me, running the t.sh test on a Dual Core AMD Opteron Server (Guest OS itself having only 1 CPU), cause a core dump as well. Trying the VM out on a server where there is only a single real physical CPU works fine without any crash. Just my findings. Not sure if anybody else is having this same issue. Lawrence
