public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "kris dot van dot hees at oracle dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3994] New: Frysk Monitor - Terminal tab - exception in giounix.c: bad file descriptor Date: Wed, 07 Feb 2007 14:26:00 -0000 [thread overview] Message-ID: <20070207142640.3994.kris.van.hees@oracle.com> (raw) I get the following exception after a random number of input lines in the Terminal tab of the Frysk Monitor: java.lang.Exception: giounix.c:400Error while getting flags for FD: Bad file descriptor (9) at org.gnu.glib.GObject.printStackTrace(libgtkjava-2.8.so) at org.gnu.gtk.Gtk.gtk_main(libgtkjava-2.8.so) at frysk.gui.Gui.gui(FryskGui) at frysk.gui.FryskGui.main(FryskGui) Sometimes it is at the first command I try to type in it, sometimes it is after 20-30 commands. But invariably, it ends up with this exception being printed at some point in time. Once this happens, and further attempts to enter input will print out the exception. Occasionally, it is followed by an endless sequence of the following error message: (Frysk:29204): Vte-WARNING **: Error reading from child: Is a directory. -- Summary: Frysk Monitor - Terminal tab - exception in giounix.c: bad file descriptor Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: kris dot van dot hees at oracle dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3994 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-02-07 14:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-07 14:26 kris dot van dot hees at oracle dot com [this message] 2007-02-07 14:39 ` [Bug general/3994] " mcvet 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=20070207142640.3994.kris.van.hees@oracle.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: 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).