Follow-up Comment #5, bug #62040 (project groff):
[comment #2 comment #2:]
> I neither get an empty line nor a memory dump.
>
> I use the most recent files in the gnulib git repository.
>
> I have eliminated those warnings from the gcc compiler (latest in the
> testing distribution of Debian), that are easy to fix.
>
Hi Bjarni,
This feedback is not as helpful as it could be. Do you know if:
1) Upgrading gnulib is, by itself, sufficient to fix the problem?
And if it isn't,
2) Which warning-suppression fix is?
And moreover, are _both_ a gnulib upgrade and a warning-suppression fix
required?
As Ingo has suggested, we don't want to fire blindly when fixing compiler
warnings. It is not sufficient to address them; we must also _understand_
them.
The above information would expedite the resolution of this bug. Failing
that, it's going to require more time and experimentation on my part.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62040>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
