From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1419 invoked by alias); 31 Oct 2003 20:01:28 -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 1406 invoked from network); 31 Oct 2003 20:01:27 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 31 Oct 2003 20:01:27 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AFfSZ-0001kr-0C; Fri, 31 Oct 2003 15:01:27 -0500 Date: Fri, 31 Oct 2003 20:01:00 -0000 From: Daniel Jacobowitz To: "J. Johnston" Cc: gdb-patches@sources.redhat.com, Andrew Cagney , kevinb@redhat.com, davidm@hpl.hp.com Subject: Re: getunwind syscall Message-ID: <20031031200126.GA6723@nevyn.them.org> Mail-Followup-To: "J. Johnston" , gdb-patches@sources.redhat.com, Andrew Cagney , kevinb@redhat.com, davidm@hpl.hp.com 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.1i X-SW-Source: 2003-10/txt/msg00884.txt.bz2 On Fri, Oct 31, 2003 at 02:28:10PM -0500, J. Johnston wrote: > More info from David. So the getunwind syscall returns data from the gate DSO? I was under the impression it was some register backing store, or similar. In that case Roland's patches for the same issue on x86 should be persued instead of using the syscall. > > -- Jeff J. > > -------- 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. Note that in the future, it won't be necessary to do a > syscall. Instead, the kernel's unwind info will be available (to the > running process) via dl_iterate_phdr(). I'm not sure though how this > is supposed to be made accessible to programs such as gdb. > > --david > > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer