From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8620 invoked by alias); 31 Oct 2003 21:42:24 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8610 invoked from network); 31 Oct 2003 21:42:23 -0000 Received: from unknown (HELO ns1.xcllnt.net) (209.128.86.226) by sources.redhat.com with SMTP; 31 Oct 2003 21:42:23 -0000 Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h9VLgFbe018455; Fri, 31 Oct 2003 13:42:15 -0800 (PST) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.10/8.12.10) with ESMTP id h9VLgFP9067568; Fri, 31 Oct 2003 13:42:15 -0800 (PST) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.10/8.12.10/Submit) id h9VLgFPR067567; Fri, 31 Oct 2003 13:42:15 -0800 (PST) (envelope-from marcel) Date: Fri, 31 Oct 2003 21:42:00 -0000 From: Marcel Moolenaar To: "J. Johnston" Cc: gdb-patches@sources.redhat.com, Andrew Cagney , kevinb@redhat.com, davidm@hpl.hp.com Subject: Re: getunwind syscall Message-ID: <20031031214215.GB67387@dhcp01.pn.xcllnt.net> References: <3FA2B7CA.5070200@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA2B7CA.5070200@redhat.com> User-Agent: Mutt/1.5.4i X-SW-Source: 2003-10/txt/msg00890.txt.bz2 On Fri, Oct 31, 2003 at 02:28:10PM -0500, J. Johnston wrote: > -------- Original Message -------- > > >>>>>On Thu, 30 Oct 2003 14:20:13 -0500, "J. Johnston" > >>>>> said: > > >> Nothing which involves a syscall is acceptable in a tdep file. > >> That's what the t means - target support. > > Andrew> Is this information available via /proc? In a core file? > > The unwind info for the Linux kernel does get included in the > core-dump (see Roland McGrath's work on this), but it is not available > via /proc. Just to be unambiguous: I assume it's only the unwind information for kernel functions that are visible and/or accessable in user space and not the unwind information for the kernel at large, and the coredump is one corresponding to a process, not the kernel; right? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net