The problem is still not solved.
Isn't that a security risk?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882454
Title:
Segfaults under deep function recursion
To manage notifications about this
** Changed in: bash (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882454
Title:
Segfaults under deep function recursion
To manage notifications about th
** Bug watch added: Debian Bug tracker #443506
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443506
** Also affects: bash (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443506
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
I can confirm that this bug is also present in the package "bash 4.2-0ubuntu3".
Another way to reproduce this bug is:
$ bash -c 'x() { x; }; x'
** Changed in: bash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882454
Title:
Segfaults under deep function recursion
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/
