summaryrefslogtreecommitdiff
path: root/open_issues/boehm_gc.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/boehm_gc.mdwn')
-rw-r--r--open_issues/boehm_gc.mdwn11
1 files changed, 10 insertions, 1 deletions
diff --git a/open_issues/boehm_gc.mdwn b/open_issues/boehm_gc.mdwn
index 0a476d71..2913eea8 100644
--- a/open_issues/boehm_gc.mdwn
+++ b/open_issues/boehm_gc.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2010, 2012, 2013 Free Software Foundation,
+[[!meta copyright="Copyright © 2010, 2012, 2013, 2014 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -199,6 +199,9 @@ sources, and for `libatomic_ops` to the
rely on glibc internals. Or we instead add support to parse
[[`/proc/`|hurd/translator/procfs]] (can even use the same as Linux?),
or use some other interface. [[!tag open_issue_glibc]]
+ This is also likely the issue causing the GDB [[!tag open_issue_gdb]]
+ `GC_find_limit_with_bound` SIGSEGV startup confusion described in
+ [[binutils]].
* `#define SIG_SUSPEND SIGUSR1`, `#define SIG_THR_RESTART SIGUSR2`
@@ -525,6 +528,12 @@ restults of GNU/Linux and GNU/Hurd look very similar.
<congzhang> and maybe c# hello world translate another day :)
+### IRC, freenode, #hurd, 2013-12-16
+
+ <braunr> gnu_srs: ah, libgc
+ <braunr> there are signal-related problems with libgc
+
+
## Leak Detection
### IRC, freenode, #hurd, 2013-10-17