This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: please help

From: fche at redhat dot com (Frank Ch. Eigler)
To: David Smith <dsmith at redhat dot com>
Cc: Breno Leitao <leitao at linux dot vnet dot ibm dot com>, Peter Teoh <htmldeveloper at gmail dot com>, systemtap at sources dot redhat dot com
Date: Tue, 14 Oct 2008 16:41:48 -0400
Subject: Re: please help
References: <e46721ab0810110701s5b1e57edt25a56f7a550fb0@mail.gmail.com> <e46721ab0810110712o721ae3e7p6b6200b6cdfea3e8@mail.gmail.com> <804dabb00810132014p448820beu7c46429834e50bf7@mail.gmail.com> <804dabb00810132032i22587182s502e33abfdc50ac9@mail.gmail.com> <48F4D936.5040904@linux.vnet.ibm.com> <48F4E8C8.90405@redhat.com>

David Smith <dsmith@redhat.com> writes:

> [...]
> It appears that systemtap is complaining that you are trying to put
> probes in a ppc (32-bit) executable while running a ppc64 (64-bit)
> kernel.  Unfortunately, that is the normal case on a ppc64 box (if I
> remember correctly).
>[...]

> If I'm reading tapsets.cxx correctly, the same problem will happen when
> trying to probe an x86 program on a system with a x86_64 kernel.

Right, this is a bug.  If uprobes can handle it, we should support
bi-architecture userspace probing, and relax the above check to assert
arch matching for the kernel side only.

- FChE

References:
- Fwd: please help
  - From: siddharam suresh
- Re: please help
  - From: Peter Teoh
- Re: please help
  - From: Peter Teoh
- Re: please help
  - From: Breno Leitao
- Re: please help
  - From: David Smith

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]