s like --buffer-size does not do what I would have expected:
[...]
--
Andrew Wood
Severity: wishlist
>
[...]
> So really it seems like -E ought to just skip 4k at once.
>
> Or at least there ought to be an option to specify the skip size. I'd
> suggest -E should take an optional argument, the skip size, and default
> to 4k.
--
Andrew Wood
oach could be linking with
> > $CC rather than $LD as autotools supply a suitable $CC. If this change
> > works natively, it'll also work for cross compilation.
>
> Thank you for the clarifications.
>
> I guess the next step is whether there should be a patch sent upstream,
> what do you think?
If you've got a patch I would gladly receive it - thanks.
--
Andrew Wood
on input), then one huge or several consecutive smaller write
> operations.
>
> > In fact, I am not sure I understand what --buffer-size does at all. :)
>
> Add me.
>
> Some light to shed on this?
--
Andrew Wood
s at the beginning of a block. So with
> > "-E 4k", an error at 2k would skip to 4k, an error at 4k would skip to 8k,
> > and so on.
> >
> > Does this seem reasonable?
>
> That sounds reasonable. Sensible, even.
--
Andrew Wood
d a work-around exists: just enclose the pipe containing pv
> into stty_g=$(stty -g); pipe | goes | here; stty $stty_g
> as I did in my reproducer above,
> so "don't panic" ;-)
>
> But maybe you can find a nice place to add this in?
> Or document the problem and the workaround?
>
> Cheers,
>
> Lars
>
> This mail was also sent
> To: p...@ivarch.com, andrew.w...@ivarch.com
> Date: Sat, 10 Feb 2018 19:07:42 +0100
> Subject: multiple pv -c : terminal left in -icanon -echo tostop
> Message-ID: <20180210180728.GH19196@soda.linbit>
--
Andrew Wood
suggestions. Don't expect a response immediately, however, they take
> their time, which is fine. :)
--
Andrew Wood
> that to compute current average rate for ETA. Looks like it works pretty
> well in this case. Also added a --rate-window option to change time window
> (default: last 10s) (name isn't great, maybe could find a better one).
--
Andrew Wood
Package: splint
Version: 1:3.1.2+dfsg-5
Severity: normal
Dear Maintainer,
I have been using splint to clean up the PV code[1], and after restructuring
src/pv/display.c, found that splint now exits with a segmentation violation
when processing that file:
*** Segmentation Violation
***
hose local variable declarations out to the block enclosing
the "switch" (line 769) stops splint from crashing out.
So it was local variable declarations inside a "case" statement that were
triggering the fault.
--
Andrew Wood
valgrind itself
behaves on that architecture.
--
Andrew Wood
11 matches
Mail list logo
