From: Lee Revell <rlrevell@joe-job.com>
To: uma@email.unc.edu
Cc: linux-kernel@vger.kernel.org, anderegg@cs.unc.edu
Subject: Re: kernel debugging
Date: Mon, 25 Jul 2005 16:02:37 -0400 [thread overview]
Message-ID: <1122321758.1472.29.camel@mindpipe> (raw)
In-Reply-To: <20050725152348.6o1f03u9r4k8cgk0@webmail1.isis.unc.edu>
On Mon, 2005-07-25 at 15:23 -0400, uma@email.unc.edu wrote:
> I am using Red Hat sources, which has function open_kcore() hardcoded to
> return -EPERM always.
>
> Changing this function to the way it is defined in the public sources (as
> shown below) did the trick.
All these Red Hat / RHEL threads are completely OT. Please take it to a
Red Hat list.
Lee
prev parent reply other threads:[~2005-07-25 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 13:15 kernel debugging UmaMaheswari Devi
2005-07-24 14:02 ` Jesper Juhl
2005-07-24 14:03 ` Jesper Juhl
2005-07-25 19:23 ` uma
2005-07-25 20:02 ` Lee Revell [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=1122321758.1472.29.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=anderegg@cs.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=uma@email.unc.edu \
/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