This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: getunwind syscall
- From: Marcel Moolenaar <marcel at xcllnt dot net>
- 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 13:42:15 -0800
- Subject: Re: getunwind syscall
- References: <3FA2B7CA.5070200@redhat.com>
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"
> >>>>><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.
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