public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "rmoseley at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4107] TestRunner is leaking file descriptors Date: Tue, 27 Feb 2007 22:26:00 -0000 [thread overview] Message-ID: <20070227222643.5822.qmail@sourceware.org> (raw) In-Reply-To: <20070227221300.4107.mcvet@redhat.com> ------- Additional Comments From rmoseley at redhat dot com 2007-02-27 22:26 ------- The limit on my FC5/i686 box for the file descriptors for TestRunner is about 1042 and then it aborts. When I run the command Mike shows I see a couple of processes running: TestRunner and funit-rt-asmstepper. Running the "lsof" command while running those, funit-rt-asmstepper appears to never open any files. If I run the "lsof" command on TestRunner I see the file descriptors run up pretty quickly until the test aborts when it reaches ~1042 fd's. Now, the weird thing is, when the test aborts, TestRunner remains in the cpu queue but it now has a *totally* PID. Doing a "lsof" on that shows about 1042 fd's open. Looking at /proc/TESTRUNNERPID/fd and doing a list I see lines and lines of this: lr-x------ 1 rmoseley rmoseley 64 Feb 27 16:06 110 -> /home/rmoseley/frysk-cvs3/build/frysk-core/frysk/pkglibdir/funit-rt-asmstepper It seems nearly all the fd's are pointing to the funit-rt-asmstepper executable. Why would the TestRunner be repeatedly opening a fd pointing to the executable? -- http://sourceware.org/bugzilla/show_bug.cgi?id=4107 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-02-27 22:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-27 22:13 [Bug general/4107] New: " mcvet at redhat dot com 2007-02-27 22:26 ` rmoseley at redhat dot com [this message] 2007-02-28 14:13 ` [Bug general/4107] " rmoseley at redhat dot com
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=20070227222643.5822.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.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).