On Thu, Jan 03, 2013 at 08:41:59PM +0800, Paul Wise wrote: > I still have the same problem on my wheezy system, the only difference > to sid is that I have libc6 2.13-37 instead of 2.13-38 and an older > version of valgrind. > > After upgrading libc6 the crash remains with the MALLOC_* variables set.
Like this? michael@feivel:~$ export MALLOC_CHECK_=2 michael@feivel:~$ export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) michael@feivel:~$ column -ets, < foo > bar column: line too long No segfault whatsoever. BTW the "line too long" message disappears if I add a final CR but no still no segfault. I also tried on a Wheezy i386 system without getting it to segfault. What kernel do you run on? The original report talked about 3.5. I'm on our Wheezy 3.2 kernel. Maybe that makes a difference. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
