Re: bash segfaulting and not being able to log in
on Sun, Mar 18, 2001 at 09:44:51PM -0500, Anthony Fox ([EMAIL PROTECTED]) wrote: Hello, I have two questions: 1. Bash segfaults when I hit tab to autocomplete a filename. I have checked the bash FAQ which does not address my specific problem. Has anyone seen this? What version of bash? In my case: $ bash --version GNU bash, version 2.04.0(1)-release (i386-pc-linux-gnu) Copyright 1999 Free Software Foundation, Inc. You've posted this problem before and we've tried a couple of things (keysyms, strace), without results. The problem is odd, I'd try at this point: - Check bash bug reports. - Keyboard test. This appears to be related to the problem. - Identify parameters of problem. - Memory test. Possible but unlikely if bash is the only problem. - Reinstall bash. If the problem persists, file a bug report. 2. I log in at the console, /etc/motd is printed, and then I am logged out. I have seen this problem on a box where home directories where NFS mounted and the NFS mount did not exist. My particular box does not have home directories mounted, but my partition table looks like: Does this happen when logging in as a regular user, as root, either? Does /etc/nologin exist? Check your .bash_profile and .bashrc files, as well as any /etc/bashrc and /etc/profile files. You might try renaming these temporarily. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpAunnanOtO5.pgp Description: PGP signature
Re: bash segfaulting and not being able to log in
kmself@ix.netcom.com writes: on Sun, Mar 18, 2001 at 09:44:51PM -0500, Anthony Fox ([EMAIL PROTECTED]) wrote: Hello, I have two questions: 1. Bash segfaults when I hit tab to autocomplete a filename. I have checked the bash FAQ which does not address my specific problem. Has anyone seen this? What version of bash? In my case: $ bash --version GNU bash, version 2.04.0(1)-release (i386-pc-linux-gnu) Copyright 1999 Free Software Foundation, Inc. GNU bash, version 2.04.0(1)-release (i386-pc-linux-gnu) You've posted this problem before and we've tried a couple of things (keysyms, strace), without results. The problem is odd, I'd try at this point: strace didn't work because auto completion using the tab key doesn't function correctly. i used gdb to debug a bash process and found the stacktrace to be failing in libreadline::autocomplete. the weird thing is that sometimes it works fine and sometimes it fails. i can't duplicate the stacktrace because bash is working fine right now. - Check bash bug reports. - Keyboard test. This appears to be related to the problem. - Identify parameters of problem. - Memory test. Possible but unlikely if bash is the only problem. - Reinstall bash. I recompiled bash from a source .deb. Last night, while /bin/bash was segfaulting, I ran the newly compiled bash and it worked just fine. The differences in sizes of the binaries is large. [EMAIL PROTECTED] ~ $ ls -l bash-2.04/bash -rwxr-xr-x 1 ant ant 1527145 Mar 18 21:54 bash-2.04/bash* [EMAIL PROTECTED] ~ $ ls -l /bin/bash -rwxr-xr-x 1 root root 404340 Nov 20 17:38 /bin/bash* The newly compiled binary is almost quadruple the size of the installed binary. It is compiled for i686-pc-linux-gnu, but I wouldn't think that would make such a difference. Should I install this version? If so, how do I install a binary that I have compiled from source? 2. I log in at the console, /etc/motd is printed, and then I am logged out. I have seen this problem on a box where home directories where NFS mounted and the NFS mount did not exist. My particular box does not have home directories mounted, but my partition table looks like: Does this happen when logging in as a regular user, as root, either? Both. Like the bash problem, it happens half the time and half the time my box works just fine. That is why I think the problems are related. Does /etc/nologin exist? Check your .bash_profile and .bashrc files, as well as any /etc/bashrc and /etc/profile files. You might try renaming these temporarily. I have checked the startup scripts, there is no problem with them. /etc/nologin does not exist. Plus, I can log in just fine half the time. Thanks for your help. Anthony
Re: bash segfaulting and not being able to log in
Lo, on , March 19, Anthony Fox did write: I recompiled bash from a source .deb. Last night, while /bin/bash was segfaulting, I ran the newly compiled bash and it worked just fine. The differences in sizes of the binaries is large. [EMAIL PROTECTED] ~ $ ls -l bash-2.04/bash -rwxr-xr-x 1 ant ant 1527145 Mar 18 21:54 bash-2.04/bash* [EMAIL PROTECTED] ~ $ ls -l /bin/bash -rwxr-xr-x 1 root root 404340 Nov 20 17:38 /bin/bash* The newly compiled binary is almost quadruple the size of the installed binary. It is compiled for i686-pc-linux-gnu, but I wouldn't think that would make such a difference. I can't be certain, but this is most probably because bash-2.04/bash has not been stripped, so it still has all of the debugging info and symbol tables in it. Try running file bash-2.04/bash It'll print out something like bash: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses shared libs), stripped If the last bit says `not stripped', then that's the deal. You can remove the extra stuff with the strip command, but these tables don't do any harm besides taking up disk space. (Since GNU/Linux, like most modern Unixes, uses demand loading, the symbol tables and such never get brought into memory.) If you do strip the stuff out, though, gdb won't be able to tell you as much useful information. In any case, if this is the reason for the size difference, this is almost certainly not related to your problem. Unfortunately, I've never experienced the sort of behavior you describe with bash, so I may not be much help. Richard
Re: bash segfaulting and not being able to log in
on Mon, Mar 19, 2001 at 09:30:28AM -0500, Anthony Fox ([EMAIL PROTECTED]) wrote: kmself@ix.netcom.com writes: on Sun, Mar 18, 2001 at 09:44:51PM -0500, Anthony Fox ([EMAIL PROTECTED]) wrote: Hello, I have two questions: ... 2. I log in at the console, /etc/motd is printed, and then I am logged out. I have seen this problem on a box where home directories where NFS mounted and the NFS mount did not exist. My particular box does not have home directories mounted, but my partition table looks like: Does this happen when logging in as a regular user, as root, either? Both. Like the bash problem, it happens half the time and half the time my box works just fine. That is why I think the problems are related. Does /etc/nologin exist? Check your .bash_profile and .bashrc files, as well as any /etc/bashrc and /etc/profile files. You might try renaming these temporarily. I have checked the startup scripts, there is no problem with them. /etc/nologin does not exist. Plus, I can log in just fine half the time. What happens if you change your user shell? Say, csh, sash, or zsh? Is anything else not working properly? This is weird behavior, and appears to be inconsistant over time, and effects different functionality. I'd suspect a hardware issue. Run a memory test and/or CPU test. Kernel compile is useful SIG11 errors tend to indicate problems. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgp0WZ3B2T2cB.pgp Description: PGP signature
