[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] Memory leak
From: |
Andrew J. Schorr |
Subject: |
Re: [bug-gawk] Memory leak |
Date: |
Tue, 28 Mar 2017 11:46:33 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Mar 28, 2017 at 08:25:19AM -0600, address@hidden wrote:
> Since you're on Linux you should have valgrind available. It would be best
> if you run valgrind on gawk in your setup.
>
> It really helps to compile gawk without optimization to get accurate
> line number info:
>
> wget http://ftp.gnu.org/gnu/gawk/gawk-4.1.4.tar.gz
> tar -xpzvf gawk-4.1.4.tar.gz
> cd gawk-4.1.4
> ./configure
> # Edit Makfile and remove -O2 from the compilation flags
> make
>
> Using the gawk you compiled, something like:
>
> # from your pipeline
> zcat sdelse1.pip.gz.5t | tail -n +2 |
> valgrind --leak-check=ful gawk -F '|' -f test.awk 2> REPORT |
> gzip > out.sdelse1.pip.gz.5t
>
> Then send us the REPORT file. This should tell us if there are real
> memory leaks or not, and will help keep Andy and me from trashing trying to
> reproduce the problem.
FYI, I ran this on the small 344-record dataset like so:
tail -n +2 sample4gnu.pip | valgrind --leak-check=full --log-file=valgrind.log
gawk -f test.awk
I then ran it on the first 200 records like so:
tail -n +2 sample4gnu.pip | head -200 | valgrind --leak-check=full
--log-file=valgrind.log.200 gawk -f test.awk
The logfiles are attached.
Regards,
Andy
valgrind.log
Description: Text document
valgrind.log.200
Description: Text document
- [bug-gawk] Memory leak, Stephane Delsert, 2017/03/27
- Re: [bug-gawk] Memory leak, arnold, 2017/03/27
- Re: [bug-gawk] Memory leak, Andrew J. Schorr, 2017/03/27
- Re: [bug-gawk] Memory leak, Stephane Delsert, 2017/03/27
- Re: [bug-gawk] Memory leak, arnold, 2017/03/28
- Re: [bug-gawk] Memory leak,
Andrew J. Schorr <=
- Re: [bug-gawk] Memory leak, arnold, 2017/03/28
- Re: [bug-gawk] Memory leak, Andrew J. Schorr, 2017/03/28
- Re: [bug-gawk] Memory leak, Stephane Delsert, 2017/03/29
- Re: [bug-gawk] Memory leak, Andrew J. Schorr, 2017/03/29
- Re: [bug-gawk] Memory leak, arnold, 2017/03/29
- Re: [bug-gawk] Memory leak, arnold, 2017/03/30
- Re: [bug-gawk] Memory leak, Andrew J. Schorr, 2017/03/30
- Re: [bug-gawk] Memory leak, Stephane Delsert, 2017/03/30
- Re: [bug-gawk] Memory leak, Andrew J. Schorr, 2017/03/30
- Re: [bug-gawk] Memory leak, Stephane Delsert, 2017/03/30