From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16260 invoked by alias); 10 Jun 2008 07:20:55 -0000 Received: (qmail 16248 invoked by uid 22791); 10 Jun 2008 07:20:53 -0000 X-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_54,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; Tue, 10 Jun 2008 07:20:27 +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 m5A7KPAR011254; Tue, 10 Jun 2008 03:20:25 -0400 Received: from pobox-2.corp.redhat.com (pobox-2.corp.redhat.com [10.11.255.15]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5A7KPHo018159; Tue, 10 Jun 2008 03:20:25 -0400 Received: from localhost.localdomain (vpn-6-18.fab.redhat.com [10.33.6.18]) by pobox-2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5A7KOD8013111; Tue, 10 Jun 2008 03:20:25 -0400 Message-ID: <484E2B37.3010309@redhat.com> Date: Tue, 10 Jun 2008 07:40:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Ray Ruvinskiy CC: frysk@sourceware.org Subject: Re: Debugging a NullPointerException in fstack References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed 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-q2/txt/msg00089.txt.bz2 Ray Ruvinskiy wrote: > Hello, Hi Ray, Thanks for the report. The first thing I would do is to file a bug at: http://sourceware.org/bugzilla/enter_bug.cgi?product=frysk To track the issue. I would not worry too much about semantics of the bug reports, or whether it is a duplicate. The report itself is valuable even if it does already exist. Typically when I file a report I'll put in whether I run Frysk from RPM, or built from source. And what OS you are running it on. And just include all the output of the tool. If fstack is failing with an NPE on some processes not others, it is most certainly a programming error somewhere. From a more in depth perspective, if you build from source, you can test the sanity of your environment particular to your system by running the Frysk testsuite. I normally cd into frysk-core/ and run ./TestRunner. You can do this from each sub-component, or if you like, run make check instead. Lastly if you want to jump straight in, fix the problem yourself, and submit a patch, try turning debug logging on with something like: ./frysk/bindir/fstack -debug frysk=FINE 1234 But even if you do try to hack on it yourself, please do file a bug and assign it to yourself. We know who is hacking on what then. Best of luck and hope to see you on IRC! Regards Phil Muldoon >