Re: [dev] Re: st: Use after free

2017-01-24 Thread tty0
January 23, 2017 11:45 AM, "hiro" <23h...@gmail.com> wrote: > nobody ever has time for me, *cry* aww ♥

Re: [dev] Re: st: Use after free

2017-01-23 Thread hiro
nobody ever has time for me, *cry*

Re: [dev] Re: st: Use after free

2017-01-23 Thread Martin Kühne
On Mon, Jan 23, 2017 at 5:48 PM, Greg Reagle wrote: > Personally I think it is despicable and anti-progress to discourage bug > reports. I specifically asked to make sure it's a bug in st, which I didn't write. And I no longer have all day to solve any problem that crosses

Re: [dev] Re: st: Use after free

2017-01-23 Thread Greg Reagle
On Mon, Jan 23, 2017, at 10:18, Alexander Keller wrote: > Now now. No need to hold contempt on the mailing lists. Suckless isn't > some Linux list where we go off on people who want to help but didn't > read the entire codebase, wiki, and archive before posting. Uh, yea it is. Where have you

Re: [dev] Re: st: Use after free

2017-01-23 Thread Martin Kühne
On Mon, Jan 23, 2017 at 4:18 PM, Alexander Keller wrote: > Now now. No need to hold contempt on the mailing lists. Suckless isn't > some Linux list where we go off on people who want to help but didn't > read the entire codebase, wiki, and archive before posting. Cool. I'll

[dev] Re: st: Use after free

2017-01-23 Thread Alexander Keller
On Mon, Jan 23, 2017, at 02:48, Martin Kühne wrote: > I had a dream last night... Now now. No need to hold contempt on the mailing lists. Suckless isn't some Linux list where we go off on people who want to help but didn't read the entire codebase, wiki, and archive before posting. However,

[dev] Re: st: Use after free

2017-01-23 Thread moosotc
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]

Re: [dev] Re: st: Use after free

2017-01-23 Thread moosotc
Martin Kühne writes: > On Mon, Jan 23, 2017 at 5:11 AM, wrote: >> What I believe[...] > > Whose responsibility would it be to test what you believe? It looks a > lot like you expect us to figure out whether you are on to something > relevant. I had a

Re: [dev] Re: st: Use after free

2017-01-22 Thread Martin Kühne
On Mon, Jan 23, 2017 at 5:11 AM, wrote: > What I believe[...] Whose responsibility would it be to test what you believe? It looks a lot like you expect us to figure out whether you are on to something relevant. I had a dream last night and in that dream I saw the glorious

[dev] Re: st: Use after free

2017-01-22 Thread moosotc
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]