Donn,
I was able to duplicate my problem in C using SIGVTALRM.
Can someone explain the impact of using -V0 ? What does it do to performance,
etc?
Mike
Sent from my iPad
On Aug 13, 2014, at 9:56 AM, Donn Cave d...@avvanta.com wrote:
[ ... re -V0 ]
Thanks, this solved the problem.
I
Donn,
Thanks, this solved the problem.
I would like to know more about what the signals are doing, and what am I
giving up by disabling them?
My hope is I can then go back to the dll expert and ask why this is causing
their library a problem and try to see if they can solve the problem from
[ ... re -V0 ]
Thanks, this solved the problem.
I would like to know more about what the signals are doing, and
what am I giving up by disabling them?
My hope is I can then go back to the dll expert and ask why this
is causing their library a problem and try to see if they can
solve the
I have some strange behavior with GHC 7.6.3 on Ubuntu 14 TLS when using FFI and
I am looking for some ideas on what could be going on.
Fundamentally, adding wait calls (delays coded in the C) changes the behavior
of the C, in that returned status codes have proper values when there are
delays,
...
Because the failures are not general in that they target one
particular value, and seem to be affected by time, it makes me
wonder if there is some subtle Haskell run time issue. Like,
could the garbage collector be interacting with things?
Does anyone have an idea what kind of things
