> Well, whose fault would it be? My default is 1M stack size, and all
> other
> programs seem to be fine with that...
Sorry, my message was confusing. This bug report was about a different
problem, the stack size one is still open. Besides, while I do agree
that memory handling should be
> > 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
On Thu, Mar 10, 2016 at 07:39:04AM +0100, Philipp Marek wrote:
> 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
Hi Michael,
> > When trying to use "column" I found an easy way to reproduce a segfault;
> > I guess it's the same here, as both data files start with whitespace.
> >
> > $ echo 'aa' | column
> > Segmentation fault
> >
> > Ie. sending a character as first character seems to cause the
On Thu, Jan 15, 2015 at 04:36:46PM +0100, Ph. Marek wrote:
> When trying to use "column" I found an easy way to reproduce a segfault;
> I guess it's the same here, as both data files start with whitespace.
>
> $ echo 'aa' | column
> Segmentation fault
>
> Ie. sending a character as
Package: bsdmainutils
Version: 9.0.6
Followup-For: Bug #691487
When trying to use column I found an easy way to reproduce a segfault;
I guess it's the same here, as both data files start with whitespace.
$ echo 'ctrl-vtabaa' | column
Segmentation fault
Ie. sending a Tab character as
6 matches
Mail list logo
