All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] strace / ptrace_offsets.h
Date: Tue, 10 Apr 2001 09:55:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005386@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005384@msgid-missing>

Gustavo Niemeyer <niemeyer@conectiva.com> writes:

|> I've just found this message from Uros in the mailing list
|> archive:
|> 
|> > I am trying to compile strace under 2.4.0-test6 and I missing symbols
|> > for PT_K_B0, PT_K_AR_PFS, PT_K_AR_UNAT, PT_K_AR_RNAT, PT_K_AR_BSPSTORE,
|> > PT_K_PR and PT_CR_IFS.  I have
|> > sucessfully compiled the same source under 2.3.99-pre6 kernel headers.
|> > 
|> > Symbol PT_CR_IFS was replaced with PT_CFM; this is a problem with strace
|> > source.  However, the other symbols disappeared from ptrace_offsets.h.
|> > I don't recall any patches against ptrace interface lately.  Is this a
|> > lossage in kernel headers?
|> 
|> Unfortunately, I haven't found any answeres to this post.
|> 
|> This problem seems to be back with strace 4.3 and kernel 2.4.3. In this
|> case, which one should be fixed??

Use the strace source from the ia64_0 branch on
cvs.strace.sourceforge.net.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5


  reply	other threads:[~2001-04-10  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10  3:11 [Linux-ia64] strace / ptrace_offsets.h Gustavo Niemeyer
2001-04-10  9:55 ` Andreas Schwab [this message]
2001-04-10 11:50 ` Gustavo Niemeyer

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=marc-linux-ia64-105590693005386@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.org \
    /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.