public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/6001] fcatch bogus output "terminated normally" Date: Mon, 31 Mar 2008 09:50:00 -0000 [thread overview] Message-ID: <20080331094956.28767.qmail@sourceware.org> (raw) In-Reply-To: <20080330154800.6001.tromey@redhat.com> ------- Additional Comments From mark at klomp dot org 2008-03-31 09:49 ------- The first issue is indeed bogus debug output. Removed: commit 91c313424052de804959314bd179a5ade351da23 Author: Mark Wielaard <mwielaard@redhat.com> Date: Mon Mar 31 11:45:51 2008 +0200 Removed debug output from ProcFollowUtil frysk-core/frysk/util/ChangeLog 2008-03-31 Mark Wielaard <mwielaard@redhat.com> * ProcFollowUtil.java (updateForkedOffspring): Remove debug output. The second issue is deliberate: frysk/util/FCatch.java // if the main thread exited print out a message that the process // terminated safely if(task.getTid() == task.getProc().getPid()){ printWriter.println(task.getProc().getPid() + "." + task.getTid() + " terminated normally"); printWriter.flush(); } I think it can be removed, or an extra option to print such informative messages. And merging fcatch with ftrace might be an interesting option indeed. -- What |Removed |Added ---------------------------------------------------------------------------- Summary|fcatch bogus output |fcatch bogus output | |"terminated normally" http://sourceware.org/bugzilla/show_bug.cgi?id=6001 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2008-03-31 9:50 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-30 15:48 [Bug general/6001] New: fcatch bogus output tromey at redhat dot com 2008-03-31 9:50 ` mark at klomp dot org [this message]
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=20080331094956.28767.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).