search for: tace

...the “you really just don’t want to go there, we know what’s best for you” aspect. Then there’s the fact that not all platforms behave the same, but we’d like a consistent set of expectations that makes it easy to use for everyone. > > So I’m leaning towards having the library serialize all tace events, because it’s a nice common denominator that every platform can implement. > > To be clear though, I don’t mean that if 2 processes are being traced simultaneously and A stops followed by B stopping, then the tool will necessarily block before handling B’s stop. I just mean that A an...

...pecially after Thernau's reply to my previous post. Assuming i'm doing well, i'd prefer to use cph because of the rms bootstrap validation facilities. Unfortunately cph doesn't wanto to model an interaction term without the both corresponding main effects: > fit.cph <- cph(TACE.Surv~PS+PS:TIME.start,data=DatasetTACE.imputati) Error in if (!length(fname) || !any(fname == zname)) { : missing value where TRUE/FALSE needed coxph runs without complaining. I could make the design matrix columns by hand, but this is generally not recommended, isn't it? Any sort of comm...

You'd probably need to pull the Unwinder in if you want backtraces, but that part shouldn't be that hard to disentangle. I don't think you'd need much else? Basing your work on NativeProcess rather than lldb proper would also cut the number of observer processes in half and avoid the context switches between the server and the debugger. That seems more appropriate for a

configure.ac | 1 test/.gitignore | 19 -- test/Makefile.am | 40 ++++ test/compiler.c | 57 ++++++ test/swfdec_test.c | 156 +++++++++++++++++ test/swfdec_test_function.c | 67 +++++++ test/swfdec_test_function.h | 35 +++ test/swfdec_test_global.c | 40

Makefile.am | 3 configure.ac | 2 doc/swfdec.types | 8 test/Makefile.am | 45 -- test/crashfinder.c | 157 ------- test/dump.c | 448 -------------------- test/swfdec-extract.c | 301 ------------- test/swfdec_out.c | 383