public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "hunt at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/4037] make staprun 32/64-bit interoperable
Date: Wed, 14 Feb 2007 02:10:00 -0000	[thread overview]
Message-ID: <20070214021026.5226.qmail@sourceware.org> (raw)
In-Reply-To: <20070214005619.4037.fche@redhat.com>


------- Additional Comments From hunt at redhat dot com  2007-02-14 02:10 -------
(In reply to comment #0)
> Please investigate why a 32-bit staprun fails to work against a 64-bit kernel. 

I intentionally disabled it because it was making a lot of code very messy. Also
I thought it provided an additional check that the systemtap you were attempting
to run was configured and compiled correctly.

The code that parses the kernel and module symbols and passes those back to the
kernel module for storage passes pointers and structures containing pointers. If
staprun has to dynamically detect mismatches and still work, that means more
complicated and potentially slower and buggier code. Still, it can be done and
isn't really a big deal, but what is the motivation?  I am confused about how
this situation occurred and why it is desireable to have 32-bit stapruns work on
64-bit kernels.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=4037

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  reply	other threads:[~2007-02-14  2:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  0:56 [Bug runtime/4037] New: " fche at redhat dot com
2007-02-14  2:10 ` hunt at redhat dot com [this message]
2007-02-14  2:28 ` [Bug runtime/4037] " fche at redhat dot com
2008-01-11 18:06 ` hunt at redhat dot com
2008-04-30 19:02 ` fche at redhat dot com
2009-11-16 20:47 ` dsmith at redhat dot com
2009-11-18  1:12 ` fche at redhat dot com
2009-11-20  8:39 ` pavan dot naregundi at in dot ibm dot com

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=20070214021026.5226.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).