ng0 <n...@we.make.ritual.n0.is> writes: > This (my.notmuch) used to work for a long time and broke today: > > ng0@shadowwalker ~$ my.notmuch > Tor mode activated. Every command will be torified for this shell. > Segmentation fault > Tor mode deactivated. Command will NOT go through Tor anymore. > > This is the same as: > > ng0@shadowwalker ~$ . torsocks on > Tor mode activated. Every command will be torified for this shell. > ng0@shadowwalker ~$ emacs -f notmuch > Segmentation fault > ng0@shadowwalker ~$ . torsocks off > bash: echo: write error: Broken pipe > Tor mode deactivated. Command will NOT go through Tor anymore. > > > torsocks version 2.2.0-rc1. I can do the same for powwow and other > applications and don't run into problems, only emacs with some -f like > notmuch segfaults. I can even run torify emacs and it works. > > > Can Someone reproduce this? I can send useful outputs and more in the > morning.
Disregard this thread, I have reported upstream (torsocks) bugs. Directly related to a recently identified and closed perl5 bug. -- ♥Ⓐ ng0 Current Keys: https://we.make.ritual.n0.is/ng0.txt For non-prism friendly talk find me on http://www.psyced.org
