On Sat, Oct 19 2019, tho...@habets.se wrote:
> On Sat, 19 Oct 2019 16:32:56 +0100, Jeremie Courreges-Anglas
> said:
>> > Before:
>> > $ HISTSIZE=10 /bin/sh
>> > /bin/sh: internal error: unable to allocate memory
>> > <--- no ksh
>> Could you provide more details please? A fatal
On Sat, 19 Oct 2019 16:32:56 +0100, Jeremie Courreges-Anglas
said:
> > Before:
> > $ HISTSIZE=10 /bin/sh
> > /bin/sh: internal error: unable to allocate memory
> > <--- no ksh
> Could you provide more details please? A fatal error and a crash are
> very different problems.
On Fri, Oct 18 2019, tho...@habets.se wrote:
> This can be hard to debug, and could indeed prevent debugging, since
> it can take out the ability to run /bin/sh, depending on how you've
> set up your environment.
>
> Before:
> $ HISTSIZE=10 /bin/sh
> /bin/sh: internal error: unable to
This can be hard to debug, and could indeed prevent debugging, since
it can take out the ability to run /bin/sh, depending on how you've
set up your environment.
Before:
$ HISTSIZE=10 /bin/sh
/bin/sh: internal error: unable to allocate memory
<--- no ksh
With this pa
$
