Summary: | USE Flag +bashlogger causes bash to segfault if length of typed command exceeds 600 chars | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Victor Nawothnig <victor.nawothnig> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Valgrind Output |
Description
Victor Nawothnig
2006-07-03 10:23:54 UTC
Forgot the bash version. 3.1_p16 works for me on x86 stable and amd64 unstable ... i tried this command: ls /../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../.. It does not depend on the gcc. I built bash with the gcc-3.4.6, gcc-4.1.0 and gcc-4.1.1 and had the same problem with each compiler. Going to try a last stable kernel today anyway. Still same error with 2.6.16-gentoo-r9. I also get the error with the standard shell. I do not have any weird or insane bash settings. Error even occurs with defaul tbash settings. Can anyone reproduce this bug, or any ideas? < marienz> norc: that backtrace makes no sense to me. It's saying bash_add_history is called with a sane value for "line", but it calls really_add_history with a null line, but I don't see any way that function could do that since it passes "line" unchanged. ^ Thats what I got in #gentoo few days ago. So maybe thats the clue that might help getting this problem fixed. Before I forget this. Of course I temporarily build bash with those settings, for debugging with gdb. CFLAGS="-O1 -pipe -g -ggdb" CXXFLAGS="${CFLAGS}" FEATURES="nostrip" But I'm having the same problem with the CFLAGS I specified. Error is due to bash-3.1-bash-logger.patch. USE="-bashlogger" solves the problem, and this flag only applies the mentioned patch. Additional valgrind output will be attached, there might be some indirect memory corruption. Hope thats enough for anyone of you to go on. Created attachment 91359 [details]
Valgrind Output
Verbose valgrind output
I attached the patch there. *** This bug has been marked as a duplicate of 91327 *** track the bug here, not in old closed/fixed bugs thanks, fix now in cvs |