Linux MIPS Architecture development
 help / color / mirror / Atom feed
* par and us*
@ 1997-08-08 15:19 Mike Shaver
  1997-08-08 15:19 ` Mike Shaver
  0 siblings, 1 reply; 2+ messages in thread
From: Mike Shaver @ 1997-08-08 15:19 UTC (permalink / raw)
  To: Linux/SGI list

I've got a simple lock-contention program that I'm using to see how
the usema stuff works.

When I try to run the program under par, though, it only lets me trace
one of the invocations:

1 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-p.par ./lock p
1 Creating new lock.
1 Storing lock.
1 Getting lock.
1 Waiting...

(now I start the second one)
2 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-c2.par ./lock c
2 Cannot syscall trace pid 23779:Resource busy
2 Finding existing lock.
2 Getting lock.
2 [shaver@linus ~/work/usema]$

(back to the shell!)
(release the lock on the first invocation)
1 
1 Releasing lock.
1 Exiting
1 [shaver@linus ~/work/usema]$ 

(and now I get more output from the second invocation)
2 [shaver@linus ~/work/usema]$ Waiting...
2 Releasing lock.
2 Exiting

Under normal circumstances (no par), I have to press enter on the
second one as well for it to release the lock and exit.  When par is
doing its (arguably weird, maybe broken) thing, I don't have to do
that...

Is this a known problem?

Mike

-- 
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation 
#>              Linux: because every cycle counts.
#>
#> "I don't know what you do for a living[...]" -- perry@piermont.com
#>        "I change the world." -- davem@caip.rutgers.edu

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

* par and us*
  1997-08-08 15:19 par and us* Mike Shaver
@ 1997-08-08 15:19 ` Mike Shaver
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Shaver @ 1997-08-08 15:19 UTC (permalink / raw)
  To: Linux/SGI list

I've got a simple lock-contention program that I'm using to see how
the usema stuff works.

When I try to run the program under par, though, it only lets me trace
one of the invocations:

1 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-p.par ./lock p
1 Creating new lock.
1 Storing lock.
1 Getting lock.
1 Waiting...

(now I start the second one)
2 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-c2.par ./lock c
2 Cannot syscall trace pid 23779:Resource busy
2 Finding existing lock.
2 Getting lock.
2 [shaver@linus ~/work/usema]$

(back to the shell!)
(release the lock on the first invocation)
1 
1 Releasing lock.
1 Exiting
1 [shaver@linus ~/work/usema]$ 

(and now I get more output from the second invocation)
2 [shaver@linus ~/work/usema]$ Waiting...
2 Releasing lock.
2 Exiting

Under normal circumstances (no par), I have to press enter on the
second one as well for it to release the lock and exit.  When par is
doing its (arguably weird, maybe broken) thing, I don't have to do
that...

Is this a known problem?

Mike

-- 
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation 
#>              Linux: because every cycle counts.
#>
#> "I don't know what you do for a living[...]" -- perry@piermont.com
#>        "I change the world." -- davem@caip.rutgers.edu

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

end of thread, other threads:[~1997-08-08 15:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1997-08-08 15:19 par and us* Mike Shaver
1997-08-08 15:19 ` Mike Shaver

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