From: David Mosberger <davidm@napali.hpl.hp.com>
To: Marcel Moolenaar <marcel@xcllnt.net>
Cc: "J. Johnston" <jjohnstn@redhat.com>,
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 23:01:00 -0000 [thread overview]
Message-ID: <16290.59848.668396.112316@napali.hpl.hp.com> (raw)
In-Reply-To: <20031031214215.GB67387@dhcp01.pn.xcllnt.net>
>>>>> On Fri, 31 Oct 2003 13:42:15 -0800, Marcel Moolenaar <marcel@xcllnt.net> said:
Marcel> 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.
Marcel> Just to be unambiguous: I assume it's only the unwind
Marcel> information for kernel functions that are visible and/or
Marcel> accessable in user space and not the unwind information for
Marcel> the kernel at large, and the coredump is one corresponding
Marcel> to a process, not the kernel; right?
Correct.
--david
prev parent reply other threads:[~2003-10-31 23:01 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
2003-10-31 23:01 ` David Mosberger [this message]
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=16290.59848.668396.112316@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=ac131313@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.com \
--cc=kevinb@redhat.com \
--cc=marcel@xcllnt.net \
/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