diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-04-17 00:16:32 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-04-17 00:16:32 +0200 |
| commit | 1dc28d745d45be6764072af1da0ceda52a0c17a3 (patch) | |
| tree | 1271b34236f2b2577185b11b1d2ade6fb1f0dbe8 /open_issues/boehm_gc.mdwn | |
| parent | a65f14df8e3d93f71acf276fb0773d6557b9fbab (diff) | |
IRC.
Diffstat (limited to 'open_issues/boehm_gc.mdwn')
| -rw-r--r-- | open_issues/boehm_gc.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/open_issues/boehm_gc.mdwn b/open_issues/boehm_gc.mdwn index ca2063a5..31359da3 100644 --- a/open_issues/boehm_gc.mdwn +++ b/open_issues/boehm_gc.mdwn @@ -332,3 +332,16 @@ It has last been run and compared on 2010-11-10, based on CVS HEAD sources from 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 :( + + +### IRC, freenode, #hurd, 2012-03-21 + + <pinotree> civodul: given we have to realtime signals (so no range of + signals for them), libgc uses SIGUSR1/2 instead of using SIGRTMIN+5/6 for + its thread synchronization stuff + <pinotree> civodul: which means that if an application using libgc then + sets its own handlers for either of SIGUSR1/2, hell breaks + <civodul> pinotree: ok + <civodul> pinotree: is it a Debian-specific change, or included upstream? + <pinotree> libgc using SIGUSR1/2? upstream + <civodul> ok |