X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 4 Feb 2008 12:03:43 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Memory leak problem reported with gfortran Message-ID: <20080204110343.GB5866@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <47A64BF1.6090808@alice.it> <47A6809F.3010100@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47A6809F.3010100@verizon.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Feb 3 19:03, Jerry DeLisle wrote: > I have continued my testing here and I am seeing this with valgrind on > linux. When I was running the 10000 loops I did not see these errors roll > by upfront initially. > > ==25454== Conditional jump or move depends on uninitialised value(s) > ==25454== at 0x4333F1: strlen (in /home/jerry/prs/pr35063/a.out) > ==25454== by 0x45DE74: fillin_rpath (in /home/jerry/prs/pr35063/a.out) > ==25454== by 0x45FC35: _dl_init_paths (in /home/jerry/prs/pr35063/a.out) > ==25454== by 0x439CDE: _dl_non_dynamic_init (in > /home/jerry/prs/pr35063/a.out) > ==25454== by 0x43A3DA: __libc_init_first (in > /home/jerry/prs/pr35063/a.out) > ==25454== by 0x414CF5: (below main) (in /home/jerry/prs/pr35063/a.out) > ==25454== > ==25454== Conditional jump or move depends on uninitialised value(s) > ==25454== at 0x4333BD: strlen (in /home/jerry/prs/pr35063/a.out) > ==25454== by 0x408087: write_integer (write.c:612) > ==25454== by 0x40AEDD: _gfortrani_list_formatted_write (write.c:785) > ==25454== by 0x400330: MAIN__ (in /home/jerry/prs/pr35063/a.out) > ==25454== by 0x40043B: main (fmain.c:21) > > The end of the run shows: > > ==25454== Use of uninitialised value of size 8 > ==25454== at 0x41AB57: exit (in /home/jerry/prs/pr35063/a.out) > ==25454== > ==25454== ERROR SUMMARY: 12 errors from 3 contexts (suppressed: 0 from 0) > ==25454== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==25454== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==25454== For counts of detected errors, rerun with: -v > ==25454== All heap blocks were freed -- no leaks are possible. > > But no memory leaks. I don't know if this is related or not. I will keep > digging. It looks suspicious. I have no trouble to imagine different kinds of problems on different OSes as a result and it wouldn't be the first time. Pitty that valgrind doesn't exist for Cygwin. At least we have strace ;) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/