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/3927] New: FryskHelpManager initial startup causes backtrace Date: Fri, 26 Jan 2007 14:51:00 -0000 [thread overview] Message-ID: <20070126145142.3927.rmoseley@redhat.com> (raw) After converting FryskHelpManager.java to use frysk.sys.Fork.daemon instead of r.exec, the initial activation(and only the initial activation) causes a backtrace, but still comes up properly. FryskHelpManager activates /usr/bin/gnome-help when the "Help" button is clicked on the first Frysk UI screen. When that button is clicked the first time the following backtrace occurs: waitpid: No child processes (process 21424) at frysk.sys.Fork.daemon(Fork.cxx:159) at frysk.sys.Fork.daemon(Fork.java:97) at frysk.gui.common.FryskHelpManager.activateHelp(FryskHelpManager.java:63) at frysk.gui.SessionManagerGui.helpSession(SessionManagerGui.java:494) at frysk.gui.SessionManagerGui$12.buttonEvent(SessionManagerGui.java:384) at org.gnu.gtk.Button.fireButtonEvent(libgtkjava-2.8.so) at org.gnu.gtk.Button.handleClick(libgtkjava-2.8.so) at org.gnu.gtk.Gtk.gtk_main(libgtkjava-2.8.so) at org.gnu.gtk.Gtk.main(libgtkjava-2.8.so) at frysk.gui.Gui.gui(Gui.java:284) at frysk.gui.FryskGui.main(FryskGui.java:88) Even thought this backtrace occurs, the proper gnome-help comes up. If the gnome-help screen is closed and the "Help" button is again clicked during the current frysk activation, no backtraces occur no matter how many times this happens. The backtrace seems to only occur on the very first activation of the gnome-help. -- Summary: FryskHelpManager initial startup causes backtrace 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 http://sourceware.org/bugzilla/show_bug.cgi?id=3927 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-01-26 14:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-26 14:51 rmoseley at redhat dot com [this message] 2007-01-29 17:10 ` [Bug general/3927] " cagney at redhat dot com 2007-01-31 21:16 ` rmoseley at redhat dot com 2007-01-31 21:39 ` cagney 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=20070126145142.3927.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: 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).