Em dom., 16 de mai. de 2021 às 22:37, Kyotaro Horiguchi <
horikyota@gmail.com> escreveu:
> At Sat, 15 May 2021 11:35:13 -0300, Ranier Vilela
> wrote in
> > Em sex., 14 de mai. de 2021 às 19:52, Tom Lane
> escreveu:
> >
> > > I wrote:
> > > > So the question for us is whether it's worth tryin
At Sat, 15 May 2021 11:35:13 -0300, Ranier Vilela wrote
in
> Em sex., 14 de mai. de 2021 às 19:52, Tom Lane escreveu:
>
> > I wrote:
> > > So the question for us is whether it's worth trying to make pgreadlink
> > > conform to the letter of the POSIX spec in this detail. TBH, I can't
> > > ge
Em sex., 14 de mai. de 2021 às 19:52, Tom Lane escreveu:
> I wrote:
> > So the question for us is whether it's worth trying to make pgreadlink
> > conform to the letter of the POSIX spec in this detail. TBH, I can't
> > get excited about that, at least not so far as zic's usage is concerned.
>
>
I wrote:
> So the question for us is whether it's worth trying to make pgreadlink
> conform to the letter of the POSIX spec in this detail. TBH, I can't
> get excited about that, at least not so far as zic's usage is concerned.
Hmmm ... on closer inspection, though, it might not be that hard.
pgr
Ranier Vilela writes:
> Per Coverity.
> CID 1412632 (#1 of 1): Out-of-bounds access (OVERRUN)1.
> overrun-buffer-val: Overrunning buffer pointed to by &c of 1 bytes by
> passing it to a function which accesses it at byte offset 4.
> For some people, Coverity opinions count zero.
This particular
