-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Blocking signals backtraces #608
Comments
Could you explain what you were doing when this message appeared? |
Just spawned fish, and second fish in the tab next to first one. Zsh 5.0 in background. Spawned from iTerm2. |
It's 100% reproductible. I just added "exec fish" at end of ~/.zshrc, and I'm spawning new tab in iterm. After that on previously opened fish console these backtraces happen (every single time) |
I do something similar, although not on OS X. Could you confirm the version of the build you are running, how you built it (Xcode or autotools) and what version of OS X you have? I wonder if your .zshrc, etc. could be poisoning your environment somehow. Are you able to |
This backtrace is reading universal variables from the daemon. There's a universal variable, and a function that watches it. When we receive the universal variable change, we run the function. That can happen at some pretty arbitrary points, in this case, determining the environment variables. In other words, fish wants to determine the environment variable array, so it reads the latest update from fishd, which changes a variable, which causes a function to run. fish 1.x had similar issues. |
@dmilith , can you please share your list of universal variables, that is, the output of |
⌘ frenziedmon:~ λ ⇒ set -UL nothing personal in here |
Thanks. The only |
I added code that enqueues event handlers if signals are blocked, instead of running them immediately. That should fix this problem. Thanks for reporting this! |
http://dmilith.verknowsys.com/Public/Sshots/s04-13:45:21.jpg
http://dmilith.verknowsys.com/Public/Sshots/s04-13:45:42.jpg
The text was updated successfully, but these errors were encountered: