bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vasnprintf.c: "out_of_memory", -Wanalyzer-free-of-non-heap, -Wanalyz


From: Bjarni Ingi Gislason
Subject: Re: vasnprintf.c: "out_of_memory", -Wanalyzer-free-of-non-heap, -Wanalyzer-malloc-leak
Date: Sun, 1 May 2022 17:16:37 +0000

On Sat, Apr 30, 2022 at 01:27:28PM -0700, Paul Eggert wrote:
> On 4/30/22 07:13, Bjarni Ingi Gislason wrote:
> >    With latest gnulib version:
> 
> I'm not seeing this problem with the current
> (84863a1c4dc8cca8fb0f6f670f67779cdd2d543b) gnulib version on Fedora 35
> x86-64, which has GCC 11.3.1 20220421 (Red Hat 11.3.1-2).
> 
> Here's how I tried to reproduce the issue:
> 
> ./gnulib-tool -h --create-testdir --dir foo vasnprintf
> cd foo
> ./configure
> make CFLAGS='-fanalyzer -Wanalyzer-mismatching-deallocation -O2' check
> 
> Does the above work for you? If so, how does it differ from what groff does?
> 
> The idea is to make the problem reproducible without dealing with groff or
> with whatever changes you made to groff. If that's not possible, I guess
> we'll need a copy of your groff source since it sounds like you've modified
> groff.

  Thanks for the method to test "vasnprintf.c" separately.

  I checked what of the about 30 options, I use for compiling "groff",
could cause the only warning (leak) about "vasnprintf.c" and it was the
"-flto".

  The compilation of "groff" then got finished with a lot of warnings
(149) about its code.

-- 
Bjarni I. Gislason



reply via email to

[Prev in Thread] Current Thread [Next in Thread]