I think the bug is located in the terminal emulation code related to
handling of alternate screens with regards to resizing. It's not
technically wrong to truncate a screen area that is located off
screen.
While we're at it, can we give you something relevant to work on?
Cheers!
mar77i
On Tue, Aug 18, 2015 at 01:43:44PM +0100, Dimitris Papastamos wrote:
Your config.h is old.
Sorry, usually it will show some error about config.h.
It seems that I still need some time rebuilding the patches.
--
_
< Do what you like, like what you do. >
---
On Tue, Aug 18, 2015 at 08:28:41PM +0800, Pickfire wrote:
> st build options:
> CFLAGS = -g -std=c99 -pedantic -Wall -Wvariadic-macros -Os -I.
> -I/usr/include -I/usr/X11R6/include -I/usr/include/freetype2
> -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2
> -I/usr/include
st build options:
CFLAGS = -g -std=c99 -pedantic -Wall -Wvariadic-macros -Os -I.
-I/usr/include -I/usr/X11R6/include -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/harfbuzz
-I/usr/include/freetype2 -I/usr/i
On Tue, Aug 18, 2015 at 12:24:03PM +0100, spaceman wrote:
Hi,
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(): inva
Quoth Gabriel Pérez-Cerezo:
> 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.
Out of curiousity, why aren't you using a HTTP/HTTPS proxy that
sends things th
spaceman wrote:
> Just a suggestion but why use torify at all if you insist on torifying
> everything. You can use IPTables to redirect all TCP (or that which want) to
> Tors TransPort. You can then block all unsafe UDP traffic. Setup a simple DNS
> server to shove DNS through Tor using the DNSPort
Hi,
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
I am using `torify surf` in arm architecture, there doesn't seems to
have any problems. I am using `torsocks` version 2.1.0 and the git
`surf`.
I just have some problems with the memory, there seems to have some
memory leak, using a window of surf for about half an hour might use
more memory comp
On Tue, Aug 18, 2015 at 12:41:51PM +0200, GhostAV wrote:
> On Tue, Aug 18, 2015 at 11:28:36AM +0100, Dimitris Papastamos wrote:
> > On Tue, Aug 18, 2015 at 12:23:12PM +0200, Gabriel Pérez-Cerezo wrote:
> > > At Tue, 18 Aug 2015 11:15:59 +0100,
> > > Dimitris Papastamos wrote:
> > > > > The command
On Tue, Aug 18, 2015 at 12:38:40PM +0200, Gabriel Pérez-Cerezo wrote:
> 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.
As i failed to send the patch to the l
It seems to be rt_tgsigqueueinfo. Here the section from my unistd.h:
#define __NR_rt_tgsigqueueinfo 240
__SC_COMP(__NR_rt_tgsigqueueinfo, sys_rt_tgsigqueueinfo, \
compat_sys_rt_tgsigqueueinfo)
--
Gabriel Pérez-Cerezo Flohr .--
GPG Key: BB0
On Tue, Aug 18, 2015 at 11:28:36AM +0100, Dimitris Papastamos wrote:
> On Tue, Aug 18, 2015 at 12:23:12PM +0200, Gabriel Pérez-Cerezo wrote:
> > At Tue, 18 Aug 2015 11:15:59 +0100,
> > Dimitris Papastamos wrote:
> > > > The command prints
> > > > [Aug 18 11:55:55] WARNING torsocks[14305]: [sys
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, Gabri
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
On Tue, Aug 18, 2015 at 12:23:12PM +0200, Gabriel Pérez-Cerezo wrote:
> At Tue, 18 Aug 2015 11:15:59 +0100,
> Dimitris Papastamos wrote:
> > > The command prints
> > > [Aug 18 11:55:55] WARNING torsocks[14305]: [syscall] Unsupported
> > > syscall number 240. Denying the call (in tsocks_sysca
At Tue, 18 Aug 2015 11:15:59 +0100,
Dimitris Papastamos wrote:
> > 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.
>
> What syscall is it?
I don't know. I
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
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
Hi. I found a bug which I call "GNU/Linux ecosystem bug", because there is no
single software where this bug is located. Steps to reproduce:
1. Open a terminal. This can be X terminal emulator, such as konsole (sic!) or
xterm. And this can be terminal multiplexer such as dvtm or tmux
2. Type the
20 matches
Mail list logo
