Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1921 - bash/glibc patch
|
DetailsNevermind, I found it. It is a bug with the new glibc.
http://lfs.osuosl.org/patches/lfs/cvs/unstable/bash-3.0-avoid_WCONTINUED-1.patch That patch fixes it all up, would you like me to file a bug report to get that patch included by default? Also fyi, there are quite a few official patches for bash (15 or 16... i think). Joshua On Wednesday 15 December 2004 04:26 pm, Joshua Rubin wrote: > Hey Guys, > I am not sure if the problem is with my systems, but on 2 boxes, if I > compile bash from abs, it jumps to 100% cpu usage on commands like "date" > and even "ls." Can anyone else confirm this, or is it my boxes? If other > people have this problem, does anyone know of a patch to fix it? It seems > to be a glibc thing from what I can tell from strace. > Joshua -- Joshua Rubin Joshua.Rubin@Colorado.EDU (303) 909-6199 |
This task depends upon
Closed by Judd Vinet (judd)
Friday, 11 February 2005, 02:09 GMT
Reason for closing: Fixed
Additional comments about closing: Okay, I've added all 16 patches.
Friday, 11 February 2005, 02:09 GMT
Reason for closing: Fixed
Additional comments about closing: Okay, I've added all 16 patches.