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/4546] New: Frysk Source window appears to have a file descriptor leak
Date: Thu, 24 May 2007 20:47:00 -0000 [thread overview]
Message-ID: <20070524214717.4546.rmoseley@redhat.com> (raw)
After bringing up a frysk source window, if you look at the "/proc/FRYSKPID/fd"
directory you will see *many* duplicate file decriptors. Here is an example of
a recent run:
ls -la /proc/8157/fd
total 0
dr-x------ 2 rmoseley rmoseley 0 May 24 10:43 .
dr-xr-xr-x 5 rmoseley rmoseley 0 May 24 10:43 ..
lrwx------ 1 rmoseley rmoseley 64 May 24 10:45 0 -> /dev/pts/4
lrwx------ 1 rmoseley rmoseley 64 May 24 10:45 1 -> /dev/pts/4
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 10 -> pipe:[33117]
l-wx------ 1 rmoseley rmoseley 64 May 24 10:45 11 -> pipe:[33117]
l-wx------ 1 rmoseley rmoseley 64 May 24 10:45 12 ->
/home/rmoseley/.frysk/logs/frysk_core_event.log.111
l-wx------ 1 rmoseley rmoseley 64 May 24 10:45 13 ->
/home/rmoseley/.frysk/logs/frysk_monitor_error.log
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 14 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 15 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 16 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 17 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 18 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 19 -> /home/rmoseley/mcvet
lrwx------ 1 rmoseley rmoseley 64 May 24 10:43 2 -> /dev/pts/4
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 20 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 21 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 22 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 23 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 24 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 25 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 26 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 27 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 28 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 29 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 3 ->
/usr/share/java/gnu-crypto-2.1.0.jar
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 30 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 31 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 32 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 33 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 34 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 35 -> /lib/libpthread-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 36 -> /lib/libpthread-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 37 -> /lib/libpthread-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 38 -> /lib/libc-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 39 -> /lib/libc-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 4 ->
/usr/share/java/gnu-crypto-2.1.0.jar
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 40 -> /lib/libc-2.4.so
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 41 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 42 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 43 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 44 -> /home/rmoseley/mcvet
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 5 -> /usr/share/java/jsse-1.0.1.jar
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 6 -> /usr/share/java/jsse-1.0.1.jar
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 7 -> /usr/share/java/bcprov-1.34.jar
lr-x------ 1 rmoseley rmoseley 64 May 24 10:45 8 -> /usr/share/java/bcprov-1.34.jar
lrwx------ 1 rmoseley rmoseley 64 May 24 10:45 9 -> socket:[33115]
Is there a fd leak somewheres of are these really necessary?
--
Summary: Frysk Source window appears to have a file descriptor
leak
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: rmoseley at redhat dot com
OtherBugsDependingO 1633
nThis:
http://sourceware.org/bugzilla/show_bug.cgi?id=4546
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-05-24 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 20:47 rmoseley at redhat dot com [this message]
2007-05-29 14:54 ` [Bug general/4546] " npremji at redhat dot com
2007-08-01 19:42 ` 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=20070524214717.4546.rmoseley@redhat.com \
--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: link
Be 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).