From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20696 invoked by alias); 26 Feb 2008 16:49:15 -0000 Received: (qmail 20689 invoked by uid 22791); 26 Feb 2008 16:49:15 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,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, 26 Feb 2008 16:48:53 +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 m1QGmp9C013486; Tue, 26 Feb 2008 11:48:51 -0500 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 m1QGmoY0016494; Tue, 26 Feb 2008 11:48:50 -0500 Received: from localhost.localdomain (vpn-6-15.fab.redhat.com [10.33.6.15]) by pobox-2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m1QGmnk5027032; Tue, 26 Feb 2008 11:48:50 -0500 Message-ID: <47C442F0.2090908@redhat.com> Date: Tue, 26 Feb 2008 16:49:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Mark Wielaard CC: Frysk Hackers Subject: Re: [stack] segment only corefiles, and [vdso] References: <47C42DF5.8030202@redhat.com> <1204041406.3487.58.camel@dijkstra.wildebeest.org> <47C437B1.3000507@redhat.com> <1204042576.3487.68.camel@dijkstra.wildebeest.org> In-Reply-To: <1204042576.3487.68.camel@dijkstra.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; 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-q1/txt/msg00081.txt.bz2 Mark Wielaard wrote: > Hi Phil, > > > I assume this is when you fstack a process that was stuck inside a > system call and it tries to do a symbol lookup? I don't know why that > would be x86 specific. It's not a very scientific statement on my behalf, just that I only observe it on IA32 not on x8664. Sorry should have qualified that up front. > But I assume you must include [vdso] because it > isn't available any other way (and even if it was on the system, then > you might be fstacking a core file that comes from a different system > that has a different vsdo layout). > > Right so --stackonly should include [vdso] then to make the corefile back trace workable. Strictly speaking we're breaking the contract there, but oh well. I think I will replace that (--stack only) option with a regex option dump instead. For example: --regex="(heap\|stack\|vdso)" or something. Phil > Cheers, > > Mark > >