On Thu, Jun 16, 2016 at 08:45:50PM +, Dan Good wrote:
> Very well, I've applied your patches as provided (except I dropped the
> trailing underscore from state.rsp_save).
Cool, thanks. I'll follow up with the more substantial changes I had
in mind when I get the chance.
>
> On Thu, Jun 16,
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 cppmagic module, I shall take
On Sun, Jun 12, 2016 at 02:10:18AM +, Dan Good wrote:
> Hairy macros? From the author of the cppmagic module, I shall take that as
> a compliment.
Touché.
That said, cppmagic is using hairy magic to do some things that are,
as far as I know, impossible by any other method. I don't think
the
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, munm
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