diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-03-20 22:44:34 +0100 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-03-20 22:44:34 +0100 |
| commit | a65f14df8e3d93f71acf276fb0773d6557b9fbab (patch) | |
| tree | c8ddf362c161781948959f4e4ecf1fbf543e0c9f /open_issues/boehm_gc.mdwn | |
| parent | d1b0d62ad9ffa33919a2997f0a9a79dddc09cee1 (diff) | |
IRC bits.
Diffstat (limited to 'open_issues/boehm_gc.mdwn')
| -rw-r--r-- | open_issues/boehm_gc.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/open_issues/boehm_gc.mdwn b/open_issues/boehm_gc.mdwn index e7f849f2..ca2063a5 100644 --- a/open_issues/boehm_gc.mdwn +++ b/open_issues/boehm_gc.mdwn @@ -321,3 +321,14 @@ It has last been run and compared on 2010-11-10, based on CVS HEAD sources from <pinotree> hmm... <pinotree> apparently enabling MMAP_ANON in mono's libgc copy was a good step, let's see + + +### IRC, OFTC, #debian-hurd, 2012-03-18 + + <pinotree> youpi: mono is afflicted by the SIGUSR1/2 conflict with libgc + <youpi> pinotree: didn't we have a solution for that? + <pinotree> well, it works just for one signal + <pinotree> the ideal solution would be having a range for RT signals, and + make libgc use RTMIN+5/6, like done on most of other OSes + <youpi> but we don't have RT signals, do we? + <pinotree> right :( |