public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: "Mao, Bibo" <bibo.mao@intel.com>
Cc: <systemtap@sources.redhat.com>
Subject: RE: About function parameter access
Date: Fri, 18 Nov 2005 22:31:00 -0000	[thread overview]
Message-ID: <20051118223102.07A2B1809B8@magilla.sf.frob.com> (raw)
In-Reply-To: Mao, Bibo's message of  Friday, 18 November 2005 16:02:30 +0800 <9FBCE015AF479F46B3B410499F3AE05B0897BE@pdsmsx405>

Sorry I was not sufficiently clear on the information required to respond
usefully to your report.  Since you have built your own kernels and only
have problems with those, I need to have the complete kernel binaries and
the complete recipe for reproducing them from the source exactly as you
have done.  Now I know what compiler to use, but that is only the first
piece of information I need.

Before putting effort into that, you should try the newest FC4 update
compiler, which is gcc-4.0.1-4.fc4; it may already have fixed some
problems.  But please note that so far I don't know whether there is any
compiler problem here at all.  I need to examine the complete kernel
binaries with their debuginfo to determine if the problem is with the
compiler producing the info or with systemtap reading it.

For the RHEL4-U2 ia64 compiler, I don't think there is a newer update of
that gcc to try.  So I just need to see the full kernel binary first thing.


Thanks,
Roland

  reply	other threads:[~2005-11-18 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18  8:02 Mao, Bibo
2005-11-18 22:31 ` Roland McGrath [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-17  5:30 Mao, Bibo
2005-11-17 22:12 ` Roland McGrath

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=20051118223102.07A2B1809B8@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=bibo.mao@intel.com \
    --cc=systemtap@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).