This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: getunwind syscall
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: "J. Johnston" <jjohnstn at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com, Andrew Cagney <ac131313 at redhat dot com>,kevinb at redhat dot com, davidm at hpl dot hp dot com
- Date: Fri, 31 Oct 2003 15:01:26 -0500
- Subject: Re: getunwind syscall
- References: <3FA2B7CA.5070200@redhat.com>
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"
> >>>>><jjohnstn@redhat.com> 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