From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16731 invoked by alias); 10 Jul 2008 17:07:36 -0000 Received: (qmail 16719 invoked by uid 22791); 10 Jul 2008 17:07:34 -0000 X-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_39,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Jul 2008 17:07:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m6AH7FY7018964 for ; Thu, 10 Jul 2008 13:07:15 -0400 Received: from pobox-3.corp.redhat.com (pobox-3.corp.redhat.com [10.11.255.67]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6AH7E4L024817; Thu, 10 Jul 2008 13:07:14 -0400 Received: from [10.14.51.26] (vpn-51-26.sfbay.redhat.com [10.14.51.26]) by pobox-3.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m6AH7Dwa014595; Thu, 10 Jul 2008 13:07:14 -0400 Message-ID: <487641C1.5010807@redhat.com> Date: Thu, 10 Jul 2008 17:07:00 -0000 From: Eric Bachalo User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Rick Moseley CC: frysk Subject: Re: Changes References: <1215663421.5233.33.camel@localhost.localdomain> <4875A151.1000200@redhat.com> <48760B1E.3060709@redhat.com> In-Reply-To: <48760B1E.3060709@redhat.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q3/txt/msg00018.txt.bz2 Rick Moseley wrote: > Sami Wagiaalla wrote: >> >>>> In particular I think Red Hat is not going to pursue Frysk's current >>>> monitoring and tracing goals, or the existing GUI. >>> >>> Perhaps this can be left as a dormant goal, to be revisited when a >>> working solution is at hand? >>> >>> A monitoring and tracing tool would be very useful. >>> >> >> Ditto. I will bring it up again when the time is right. >> >> > Agreed too. The ability to catch a task as it is abnormally terminating > and bring up the debugger is a powerful thing IMHO. I don't see any > need here to involve another app(Systemtap has been mentioned) to > perform this feature. I don't remember this being too difficult in > Frysk(although I am not the one that implemented it.) The tracing features is an area I would like to investigate when we look at making frysk and systemtap work closely together. But I want to see a robust debugging app working first. I would also like to see investigation into using systemtap or using same interface to OS that systemtap uses, or using prebuilt tapsets, to implement fast and efficient conditional breakpoints / watchpoints / catchpoints. - Eric