On Sun, Jan 3, 2016 at 8:24 AM, Eduardo A. Bustamante López
wrote:
> On Sat, Jan 02, 2016 at 03:08:54PM +0200, Joey Geralnik wrote:
>> I have found an easily reproducible bug in bash that causes it to crash and
>> have attached a fix.
>
> I think this was already reported [..]
> And I think the fi
I didn't check the devel branch but reading the previous bug report it's
the same issue. So if it's fixed in devel all should be good
On Jan 3, 2016 12:36 PM, "Piotr Grzybowski" wrote:
> On Sun, Jan 3, 2016 at 8:24 AM, Eduardo A. Bustamante López
> wrote:
> > On Sat, Jan 02, 2016 at 03:08:54PM +
On 12/31/15 7:04 PM, nerdopolis wrote:
> I tested on
> 4.2.45(1)-release
>
> basically I have tested
> nerdopolis@nerdopolis:~$ readonly POSIXLY_CORRECT=1
> nerdopolis@nerdopolis:~$ set +o posix
> nerdopolis@nerdopolis:~$ echo $POSIXLY_CORRECT
>
> nerdopolis@nerdopolis:~$
>
> Although I will ad
On 1/2/16 8:08 AM, Joey Geralnik wrote:
> I have found an easily reproducible bug in bash that causes it to crash and
> have attached a fix.
Thanks for the report. Your analysis is spot on.
This was reported and fixed back in July, 2015:
http://lists.gnu.org/archive/html/bug-bash/2015-07/msg000
Hi,
Im not sure if this is a regression because I already found another bug report
with the same symptoms from 2007, but when adding this line to the
/etc/rc.local the cpu usage of one of the two cores raises to 100%:
su cubie -c "(cd /home/cubie/Haussteuerung/Haussteuerung; ./run.sh)" &
When
It's impossible to tell with the amount of info you provided. That's why
there's a 'bashbug' script alongside bash to generate a useful bug report
template.
Provide:
- bash version: bash --version
- OS name and version: uname -a
- The contents of the run.sh file
- If possible also the su version
