Re: reclaiming memory before exit

On Sat, 2020-05-16 at 01:03 +0200, Bruno Haible wrote: > Well, my experience is different. Last month, I analyzed a program > that uses GNU libtextstyle, and the valgrind "leak" reports could be > categorized into three groups: > * 1056 + 296 + 56 bytes, allocated through

Re: reclaiming memory before exit

Jeffrey Walton wrote: > Allow me to rephrase again as if I am speaking to executives: GNU > should embrace a diversity of leadership. This topic is off-topic on this list. Please don't discuss it here. First, read [1]. Then, you can discuss it privately with Richard Stallman and the members of

Re: Remove license modules

Hi, Asher Gordon wrote: > Since Savannah requires licenses to be under version control (see > here¹), I don't think it makes sense for Gnulib to provide modules for > them. My reasoning is that if developers are going to use a Gnulib > module, they won't keep the files it provides under version

Re: reclaiming memory before exit

On Fri, May 15, 2020 at 6:07 PM Paul Smith wrote: > > On Fri, 2020-05-15 at 16:38 -0400, Jeffrey Walton wrote: > > On Fri, May 15, 2020 at 4:23 PM Paul Eggert > > > To fix this problem you need to fix GNU itself. They need new blood > > in leadership that understands and embraces modern

Re: reclaiming memory before exit

Hi Paul, > One issue is whether it's OK for test suites to leak memory (in the > classic sense) because it's "just a test". I'm of the opinion that > tests should not contain those types of memory leaks and if someone > comes along with a fix, it should be applied. I don't think it's >

Re: reclaiming memory before exit

On Fri, 2020-05-15 at 21:58 +0200, Bruno Haible wrote: > Another possibility is to standardize on a GCC attribute for > functions, with the meaning "memory allocations done inside this > functions are on the same level as static initializations and don't > need to be reclaimed before program

Re: reclaiming memory before exit

On Fri, 2020-05-15 at 16:38 -0400, Jeffrey Walton wrote: > On Fri, May 15, 2020 at 4:23 PM Paul Eggert > wrote: > > On 5/15/20 10:52 AM, Kamil Dudka wrote: > > > I do not understand why you take it personally. > > > > I didn't take it personally. The email in question wasn't even > > directed at

Re: reclaiming memory at dlclose time

Jeffrey Walton wrote: > The use case is incomplete. It does not cover libraries. > > Just ask the OpenJDK guys about libraries like Ncurses and OpenSSL. > They were discussing library problems on the OpenSSL mailing list in > the past. > > You see, the application will remain loaded, but Java

Re: c-stack.c and DEBUG: missing import

Hi Paul, > I don't think we need to go that far, since c-stack is already using > ignore_value. I installed the attached. You beat me to it by 2 minutes :) I verified that the patch fixes the warning that occurred with ./configure CPPFLAGS="-Wall -DDEBUG" --with-libsigsegv-prefix=... Bruno

Re: c-stack.c and DEBUG: missing import

On 5/14/20 7:01 AM, Marc Nieper-Wißkirchen wrote: > This will be a nice use case for the newly created attribute module > and MAYBE_UNUSED. I don't think we need to go that far, since c-stack is already using ignore_value. I installed the attached. >From c8c5f321dd10b21c8ad55f5c134c93235ffc9930

Re: reclaiming memory before exit

On Fri, May 15, 2020 at 4:23 PM Paul Eggert wrote: > > On 5/15/20 10:52 AM, Kamil Dudka wrote: > ... > > I do not understand why you take it personally. > > I didn't take it personally. The email in question wasn't even directed at > me. I > do value civility, though. There was nothing uncivil

Re: reclaiming memory before exit

On 5/15/20 10:52 AM, Kamil Dudka wrote: > There are certainly many > modern software projects that have higher requirements on cleanup of resources Sure, just as there used to be software projects that had "higher" requirements on using the Hungarian notation. Although those requirements may

Re: reclaiming memory before exit

On Fri, May 15, 2020 at 3:58 PM Bruno Haible wrote: > > Kamil Dudka wrote: > > How old is the text in GNU standards that Bruno refers to? > > How old it is, is irrelevant because the two main points are valid and will > continue to be valid (if the tools don't change): > > 1) The sentence "if

Re: reclaiming memory before exit

Kamil Dudka wrote: > How old is the text in GNU standards that Bruno refers to? How old it is, is irrelevant because the two main points are valid and will continue to be valid (if the tools don't change): 1) The sentence "if memory is used until just before a process exits, don’t free it

Re: reclaiming memory before exit

On Friday, May 15, 2020 5:16:28 AM CEST Paul Eggert wrote: > On 5/14/20 5:11 PM, Jeffrey Walton wrote: > > Not everyone has GNU's low standards. > > Now may be a good time to remind us of the GNU Kind Communications > Guideline; see . >

Re: gcc -fanalyze

On Friday, May 15, 2020 5:11:40 AM CEST Paul Eggert wrote: > On 5/14/20 1:34 AM, Kamil Dudka wrote: > > Now I see that we can just > > build coreutils with -Dlint even for binary RPMs without any drawbacks. > > Good, and that also means you don't need the coreutils-8.32-if-lint.patch > that you

Re: reclaiming memory before exit

Jeffrey, > > We discussed this already in the thread starting at [1]. > > Not everyone has GNU's low standards. You are one of the few persons who apply analysis and checking tools to many GNU projects, more than anyone else [2][3]. This is appreciated (as long as the reports are about