Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marcel Moolenaar <marcel@xcllnt.net>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com,
	Andrew Cagney <ac131313@redhat.com>,
	kevinb@redhat.com, davidm@hpl.hp.com
Subject: Re: getunwind syscall
Date: Fri, 31 Oct 2003 21:42:00 -0000	[thread overview]
Message-ID: <20031031214215.GB67387@dhcp01.pn.xcllnt.net> (raw)
In-Reply-To: <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


  parent reply	other threads:[~2003-10-31 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 19:28 J. Johnston
2003-10-31 20:01 ` Daniel Jacobowitz
2003-10-31 21:02   ` J. Johnston
2003-10-31 22:49   ` David Mosberger
2003-10-31 21:42 ` Marcel Moolenaar [this message]
2003-10-31 23:01   ` David Mosberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031031214215.GB67387@dhcp01.pn.xcllnt.net \
    --to=marcel@xcllnt.net \
    --cc=ac131313@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=kevinb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox