* Display of .statement(NUM) for 64 bits
@ 2008-05-23 16:30 Wenji Huang
2008-05-24 4:42 ` Frank Ch. Eigler
0 siblings, 1 reply; 2+ messages in thread
From: Wenji Huang @ 2008-05-23 16:30 UTC (permalink / raw)
To: systemtap
Hi,
This may be not an error, just about output for .statement(NUM) on 64
bits machine.
It is like:
$ stap -u -p2 -e 'probe kernel.statement(0xffffffff8040beb0) {}'
# probes
kernel.statement(-2143240528) /* pc=0x202eb0 */ /* <-
kernel.statement(-2143240528) */
The minus is outputted and also kept in C file. Seems hex is better.
Regards,
Wenji
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Display of .statement(NUM) for 64 bits
2008-05-23 16:30 Display of .statement(NUM) for 64 bits Wenji Huang
@ 2008-05-24 4:42 ` Frank Ch. Eigler
0 siblings, 0 replies; 2+ messages in thread
From: Frank Ch. Eigler @ 2008-05-24 4:42 UTC (permalink / raw)
To: Wenji Huang; +Cc: systemtap
Wenji Huang <wenji.huang@oracle.com> writes:
> This may be not an error, just about output for .statement(NUM) on
> 64 bits machine. [probe points disassemble to decimal integers]
We could tweak this by adding heuristics to probe_point::print() so as
to print small numbers in decimal and large ones in hex. (Remember,
number parameters also appear in probe begin(N), timer.s(N), etc.)
- FChE
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-05-23 12:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-05-23 16:30 Display of .statement(NUM) for 64 bits Wenji Huang
2008-05-24 4:42 ` Frank Ch. Eigler
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).