Changes between Initial Version and Version 1 of Ticket #366, comment 2


Ignore:
Timestamp:
Aug 30, 2016, 12:00:43 AM (3 years ago)
Author:
dmik
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #366, comment 2

    initial v1  
    1 Hmm, there is a `umForkCompletion` callback that does exactly that: releases LIBC heaps in the child. However, it seems to be called **after** the callback I add in reply to !__LIBC_FORK_OP_FORK_PARENT. Which is because completion callbacks are called in LIFO order and and my callback is installed much later than `umForkCompletion` (added in from the parent callback with priority 0xffffff01). I need to try using a higher priority for my parent callback, something like 0xfffffff (the highest one).
     1Hmm, there is a `umForkCompletion` callback that does exactly that: releases LIBC heaps in the child. However, it seems to be called **after** the callback I add in reply to !__LIBC_FORK_OP_FORK_PARENT. Which is because completion callbacks are called in LIFO order and and my callback is installed much later than `umForkCompletion` (added in reply to !__LIBC_FORK_OP_EXEC_PARENT called with priority 0xffffff01). I need to try using !__LIBC_FORK_OP_EXEC_PARENT as well and a higher priority for my parent callback, something like 0xfffffff (the highest one).