Re: [ccan] [PATCH 5/5] altstack: Don't log internal calls in test cases

2016-06-16 Thread Dan Good
Very well, I've applied your patches as provided (except I dropped the trailing underscore from state.rsp_save). On Thu, Jun 16, 2016 at 7:12 AM David Gibson wrote: > On Sun, Jun 12, 2016 at 02:10:18AM +, Dan Good wrote: > > Hairy macros? From the author of the

Re: [ccan] [PATCH 5/5] altstack: Don't log internal calls in test cases

2016-06-11 Thread Dan Good
Hairy macros? From the author of the cppmagic module, I shall take that as a compliment. The purpose of the setcall macro and related checks is ensure the correctness of the error path, i.e. if setrlimit ran before a failure, it must run again to undo the first; if mmap ran before a failure,

[ccan] [PATCH 5/5] altstack: Don't log internal calls in test cases

2016-06-03 Thread David Gibson
altstack/test/run.c uses some hairy macros to intercept the standard library functions that altstack uses. This has two purposes: 1) to conditionally cause those functions to fail, and thereby test altstack's error paths, and 2) log which of the library functions was called in each testcase. The