moos...@gmail.com writes:
> `valgrind st -f mono-2 cat full-bmp.txt' [1]
>
> Yields quite a few invalid reads from freed blocks, the issue is related
> to cache management. In the real world those dangling pointer issues
> lead to segfaults or X11 errors (eventually)
>
> [1] http://www.cl.cam.ac.u
d in that dream I saw the
> glorious future of a moosotc figuring things out on his own. The
> issues, progress and the personal role that derives from what we
> accomplish this way is what gets us to places in life.
>
I don't think it's anyones responsibility, just that people
moos...@gmail.com writes:
> `valgrind st -f mono-2 cat full-bmp.txt' [1]
>
> Yields quite a few invalid reads from freed blocks, the issue is related
> to cache management. In the real world those dangling pointer issues
> lead to segfaults or X11 errors (eventually)
>
> [1] http://www.cl.cam.ac.u
Hiltjo Posthuma writes:
> On Sun, Jan 22, 2017 at 11:00:28PM +0300, moos...@gmail.com wrote:
>> Martin Kühne writes:
>>
>> > On Sun, Jan 22, 2017 at 5:17 PM, wrote:
>> >>
>> >> `valgrind st -f mono-2 cat full-bmp.txt' [1]
>> >>
>> >> Yields quite a few invalid reads from freed blocks, the iss
Martin Kühne writes:
> On Sun, Jan 22, 2017 at 5:17 PM, wrote:
>>
>> `valgrind st -f mono-2 cat full-bmp.txt' [1]
>>
>> Yields quite a few invalid reads from freed blocks, the issue is related
>> to cache management. In the real world those dangling pointer issues
>> lead to segfaults or X11 er
`valgrind st -f mono-2 cat full-bmp.txt' [1]
Yields quite a few invalid reads from freed blocks, the issue is related
to cache management. In the real world those dangling pointer issues
lead to segfaults or X11 errors (eventually)
[1] http://www.cl.cam.ac.uk/~mgk25/ucs/full-bmp.txt
--
mailto:
moos...@gmail.com writes:
> Hello,
>
> I grew accustomed to button3 behavior in rxvt and wanted to add
> something similar to st, my attempt sort of works but is not ideal and
> not what rxvt does, here's the diff:
[..snip..]
>
>
> This is on top of st-scrollback-0.7.diff. Any help in matching
Hello,
I grew accustomed to button3 behavior in rxvt and wanted to add
something similar to st, my attempt sort of works but is not ideal and
not what rxvt does, here's the diff:
@@ -989,6 +996,19 @@ bpress(XEvent *e)
sel.tclick2 = sel.tclick1;
sel.tclick1 = now;
