?  search:
summary | log | graphiclog1 | graphiclog2 | commit | commitdiff | tree | refs | edit | fork
blame | history | raw | HEAD
Check some known PATHs for mpicc in configure.
[valgrind.git] / drd / tests / sigaltstack.stderr.exp
blobb95833f61726e374dd1db26073ace7388cd229bd
1 calling sigaltstack, stack base is 0x........
2 setting sigaction
3 res = 0
4 raising the signal
5 caught signal, local var is on 0x........
6 done
Instrumentation framework for detecting many memory management and threading bugs, and profile your programs in detail.