From: Jes Sorensen <jes@linuxcare.com>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] glibc and ptrace
Date: 19 Dec 2000 20:59:49 +0100 [thread overview]
Message-ID: <d366kg5gi2.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Richard Hirst's message of "Tue, 19 Dec 2000 18:22:57 +0000"
>>>>> "Richard" == Richard Hirst <rhirst@linuxcare.com> writes:
Richard> So, should I be fixing glibc (if removing that line is indeed
Richard> a fix), or should I be fixing our kernel source so the glibc
Richard> wrapper isn't needed? ia64, for example seems to fix it in
Richard> the kernel, while sparc64 looks like it uses the glibc
Richard> wrapper.
I'd say fix it in the kernel if it's cheaper to do so. You can stick a
wrapper in glibc as well, but it sounds to be simpler to do in the
kernel.
Jes
next prev parent reply other threads:[~2000-12-19 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 18:22 [parisc-linux] glibc and ptrace Richard Hirst
2000-12-19 19:59 ` Jes Sorensen [this message]
2000-12-19 20:14 ` Richard Hirst
2000-12-19 20:39 ` Jes Sorensen
2000-12-21 13:19 ` Richard Hirst
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=d366kg5gi2.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=rhirst@linuxcare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.