-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Abort trap: 6" messages in bash #262
Comments
Are you on a macOS? have you tried rebooting your machine? |
Yes, and it didn't help. |
feel free to re-open if this comes back or if you figure out what it was. This is likely an issue with a couple of poorly written things (my thing included) not interacting well. |
I’m having this issue at the moment and can mitigate it by disabling z (v 1.9). Interestingly it only happens if I am not in my home directory. Not sure what I did to trigger it, but brew may have updated |
I think it's an interaction with something else maybe doing something like Not surprising it doesn't happen in are you using bash or zsh? |
I use bash. Thanks for the tip. After sourcing Note the missing semicolon after my call to |
ah, makes some sense. definitely a challenge to keep everything playing nice when other stuff is hooking in |
Very good shout! It was actually my dotfiles that were omitting the semicolon. I’ve resolved that now. Typically, I checked that I had solved the semicolon with #269 but didn’t check that it resolved the Running the actually
A little Googling suggested upgrading Thanks for your help. You may wish to close this. I have an improvement to #269 which feels sensible but that isn’t relevant to this. |
All of a sudden, I am getting "Abort trap: 6" messages in my terminal after each command. Removing the "~/.z" database do not help and the issue persists restarts. Only disabling z (not sourcing z.sh) gets rid of the problem. I haven't plowed through the z.sh file to identify where the error message might be coming from, so any help welcome.
The text was updated successfully, but these errors were encountered: