It really seems to be a problem with torsocks. I have already solved this problem with a patch GhostAV just sent me on this list that adds SOCKS support to surf. It works fine now. At Tue, 18 Aug 2015 11:32:48 +0100, Dimitris Papastamos wrote: > > On Tue, Aug 18, 2015 at 12:00:40PM +0200, Gabriel Pérez-Cerezo wrote: > > Hello, > > > > I run surf through tor using 'torify surf'. If I don't add the '-i' > > option, it segfaults when searching on Duckduckgo. Even if I add the > > '-i' flag, it crashes after some time with messages like > > "*** Error in `surf': free(): invalid pointer: 0x095ca248 ***" > > or a segmentation fault and often reaches 100% CPU usage. Can you > > replicate this situation? > > > > The command prints > > [Aug 18 11:55:55] WARNING torsocks[14305]: [syscall] Unsupported > > syscall number 240. Denying the call (in tsocks_syscall() at syscall.c:165) > > to STDOUT. > > Looking at the torsocks code, it seems they do handle futexes[0]. Can > you try a newer version of torsocks or directly from git? > > [0] https://gitweb.torproject.org/torsocks.git/tree/src/lib/syscall.c#n428 >
-- Gabriel Pérez-Cerezo Flohr .------------------------------------------ GPG Key: BB09BA34D353EC69 / Email is like a postcard, anyone can read Website: http://gpcf.eu / it. Please use the GPG Key to encrypt your Email: gabr...@gpcf.eu / emails (tutorial: emailselfdefense.fsf.org).
