public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/25728] New: File descriptor leak in Date: Mon, 09 Jan 2006 19:54:00 -0000 [thread overview] Message-ID: <bug-25728-682@http.gcc.gnu.org/bugzilla/> (raw) verify-lines in gcc/testsuite/lib/gcov.exp has proc verify-lines { testcase file } { #send_user "verify-lines\n" set failed 0 set fd [open $file r] while { [gets $fd line] >= 0 } { if [regexp "^ *(\[^:]*): *(\[0-9\]+):.*count\\((\[0-9\]+)\\)" \ "$line" all is n shouldbe] { if { $is == "" } { fail "$n:no data available for this line" incr failed } elseif { $is != $shouldbe } { fail "$n:is $is:should be $shouldbe" incr failed } } } return $failed } There is no "close $fd", which leads to file descriptor leak. -- Summary: File descriptor leak in Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl at lucon dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25728
next reply other threads:[~2006-01-09 19:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-09 19:54 hjl at lucon dot org [this message] 2006-01-09 19:59 ` [Bug testsuite/25728] File descriptor leak in lib/gcov.exp hjl at lucon dot org 2006-01-12 1:29 ` hjl at gcc dot gnu dot org 2006-01-12 1:35 ` hjl at gcc dot gnu dot org 2006-01-12 1:40 ` hjl at gcc dot gnu dot org 2006-01-12 1:45 ` hjl at gcc dot gnu dot org 2006-01-12 1:47 ` hjl at lucon dot org 2006-01-28 21:20 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25728-682@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).