public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec
@ 2002-01-25  9:28 Weihaw Chuang
  2002-01-25 16:30 ` David Mosberger
  2002-01-25 20:01 ` David Mosberger
  0 siblings, 2 replies; 3+ messages in thread
From: Weihaw Chuang @ 2002-01-25  9:28 UTC (permalink / raw)
  To: linux-ia64

Hi folks,
I'm using the ptrace interface to create a
"architectural" processor state tracing tool.  When I
access AR.LC and AR.EC, I *usually* get the expected
result, but every once and a while it returns a bogus
result.

Is there a known bug, or am I using ptrace
incorrectly?

Here's how its used:
lc = ptrace (PTRACE_PEEKUSER, state->pid, PT_AR_LC,
0);

The tracing program observes some sort of behavior
like:

mov.i ar.lc = r61    (I'm pretty sure r61 is 6), and  
                       ptrace returns 0 
sxt4  r22=r60        ptrace returns -1
.....                "
(swp kernel code)    "
.....                "
br.ctop.sptk.few .b9 ptrace returns -1, br taken 
(p17) st8 [r15]=r34  ptrace returns 5

Many thanks,
-Wei


==************************************************************

Weihaw Chuang
wchuang@cs.ucsd.edu

************************************************************

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec
  2002-01-25  9:28 [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec Weihaw Chuang
@ 2002-01-25 16:30 ` David Mosberger
  2002-01-25 20:01 ` David Mosberger
  1 sibling, 0 replies; 3+ messages in thread
From: David Mosberger @ 2002-01-25 16:30 UTC (permalink / raw)
  To: linux-ia64

 > Hi folks,
 > I'm using the ptrace interface to create a
 > "architectural" processor state tracing tool.  When I
 > access AR.LC and AR.EC, I *usually* get the expected
 > result, but every once and a while it returns a bogus
 > result.

 > Is there a known bug, or am I using ptrace
 > incorrectly?

Not a known bug.

 > Here's how its used:
 > lc = ptrace (PTRACE_PEEKUSER, state->pid, PT_AR_LC,
 > 0);

 > The tracing program observes some sort of behavior
 > like:

 > mov.i ar.lc = r61    (I'm pretty sure r61 is 6), and  
 >                        ptrace returns 0 
 > sxt4  r22=r60        ptrace returns -1
 > .....                "
 > (swp kernel code)    "
 > .....                "
 > br.ctop.sptk.few .b9 ptrace returns -1, br taken 
 > (p17) st8 [r15]=r34  ptrace returns 5

Do you have a self-contained and small test program that reproduces
the problem?  That would make it easier to investigate the problem.

	--david


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec
  2002-01-25  9:28 [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec Weihaw Chuang
  2002-01-25 16:30 ` David Mosberger
@ 2002-01-25 20:01 ` David Mosberger
  1 sibling, 0 replies; 3+ messages in thread
From: David Mosberger @ 2002-01-25 20:01 UTC (permalink / raw)
  To: linux-ia64

Hi Wei,

>>>>> On Fri, 25 Jan 2002 08:43:28 -0800 (PST), wei@baldursgate.ucsd.edu said:

  Wei> Hi David, Thanks for replying.  Here's a reduced testcase that
  Wei> replicates the result.  Its derived from the utrace.c program
  Wei> you gave me a long time ago.

I can't reproduce the problem with 2.4.17.

  Wei> I'm currently using "Linux version 2.4.3-12smp" "Red Hat Linux
  Wei> 7.1 2.96-85".

That's a very old kernel.  Can you try after upgrading to something
more recent?

Thanks,

	--david


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-01-25 20:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-25  9:28 [Linux-ia64] ptrace behavior accessing ar.lc and ar.ec Weihaw Chuang
2002-01-25 16:30 ` David Mosberger
2002-01-25 20:01 ` David Mosberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox