From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6244 invoked by alias); 26 Feb 2008 16:16:38 -0000 Received: (qmail 6236 invoked by uid 22791); 26 Feb 2008 16:16:37 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (83.160.170.119) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 26 Feb 2008 16:16:18 +0000 Received: from dijkstra.wildebeest.org ([192.168.1.29]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1JU2TY-00043X-7G; Tue, 26 Feb 2008 17:16:16 +0100 Subject: Re: [stack] segment only corefiles, and [vdso] From: Mark Wielaard To: Phil Muldoon Cc: Frysk Hackers In-Reply-To: <47C437B1.3000507@redhat.com> References: <47C42DF5.8030202@redhat.com> <1204041406.3487.58.camel@dijkstra.wildebeest.org> <47C437B1.3000507@redhat.com> Content-Type: text/plain Date: Tue, 26 Feb 2008 16:16:00 -0000 Message-Id: <1204042576.3487.68.camel@dijkstra.wildebeest.org> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) 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/msg00078.txt.bz2 Hi Phil, On Tue, 2008-02-26 at 16:00 +0000, Phil Muldoon wrote: > Mark Wielaard wrote: > > On Tue, 2008-02-26 at 15:19 +0000, Phil Muldoon wrote: > >> When I implemented that experimental feature, I only included the > >> [stack] segment. However on IA32, there is always a visit to the [vdso] > >> segment which I did not include. > > > > What is the visit from/for? > > Well it appears to happen on every IA32 process. Why/to ... not terribly > sure other than every process/corefile seems to include a visit there. > just fstack a 32 bit process. 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. 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). Cheers, Mark