RE: [Monotone-devel] Solaris breakage

[Kelly F. Hickel]

> 
> On 7/24/07, Zack Weinberg <address@hidden> wrote:
> > Aha, you're the one with the Solaris box!  Please do exactly what I
> > suggested in my original comment on this problem - run the test case
> > up to right *before* the failing command [put "check(false)" in the
> > relevant __driver__.lua, immediately before the failing command] and
> > then run the failing command from the shell under truss(1) [strace(1)
> > is better if you have it] and mail in the complete output.
[Kelly F. Hickel] Ahh, but you didn't give *Exact* commands!  I'm not (yet) a 
monotone user, so the more exact the better.

If you can give me the command to just run this one test, that would help, if 
not it will be a long time before the tests complete, so maybe we'll have the 
results tomorrow.
> 
> Addendum: I dimly remember Solaris boxes having a program named
> strace, or possibly trace, that has nothing to do with system-call
> tracing.  If the manpage for strace does not start with
> 
> NAME
>        strace - trace system calls and signals
> 
> then it is not the program we want.  It might be called sctrace
> instead; or just use truss, which definitely does what we want, just
> with less helpful output.
[Kelly F. Hickel] I think you mean dtrace, that's possible, but if I have to 
run the whole test suite up to that point under dtrace, it's gonna take days, 
and the output will be huge....
> 
> zw

-Kelly