> > Well, it only got easier - just start it: > > > > $ column > > Speicherzugriffsfehler > > ... > > Let me guess, you've set ulimits on the process? column needs quite a bit of > heap space for statically allocated buffers. Yes, it'd be nice if it was > patched to use malloc, but the segfault is not really columns fault in this > case. Yeah, right!
Thanks for the tip... somewhere between "ulimit -s4100" and "ulimit -s4200" there's the limit for being able to start column. Well, whose fault would it be? My default is 1M stack size, and all other programs seem to be fine with that... Thank you very much, and sorry for the noise.
