Skip Menu |
 

This queue is for tickets about the Test-RunValgrind CPAN distribution.

Report information
The Basics
Id: 119988
Status: open
Priority: 0/
Queue: Test-RunValgrind

People
Owner: Nobody in particular
Requestors: bkb [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Suggest not testing that zero bytes are in use
Download (untitled) / with headers
text/plain 656b
In the program, https://github.com/shlomif/perl-Test-RunValgrind/blob/master/Test-RunValgrind/lib/Test/RunValgrind.pm#L62 you require that it says exactly "in use at exit: 0 bytes". To get that requires closing stdout or not using printf. If one uses printf, a buffer is allocated which is tied to stdout, and is not freed until one does fclose (stdout). That is rather an annoying requirement and it doesn't indicate that there is an error in the program that more than zero bytes are in use at exit, since the bytes are freed by _exit when it closes stdout. Sorry to report so many bugs at once, I promise this will be the last until I hear from you.
Download (untitled) / with headers
text/plain 1006b
On Wed Jan 25 21:58:01 2017, BKB wrote: Show quoted text
> In the program, > > https://github.com/shlomif/perl-Test-RunValgrind/blob/master/Test- > RunValgrind/lib/Test/RunValgrind.pm#L62 > > you require that it says exactly "in use at exit: 0 bytes". To get > that requires closing stdout or not using printf. If one uses printf, > a buffer is allocated which is tied to stdout, and is not freed until > one does fclose (stdout). That is rather an annoying requirement and > it doesn't indicate that there is an error in the program that more > than zero bytes are in use at exit, since the bytes are freed by _exit > when it closes stdout. > > Sorry to report so many bugs at once, I promise this will be the last > until I hear from you.
Hi BKB! Sorry for the late reply. I personally wish this check to be present but I would welcome an *optional* flag to skip it preferably with the necessary refactoring and automated tests added, as a github pull-request to https://github.com/shlomif/perl-Test-RunValgrind .


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.