You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently a bug in the Sigar Ruby C extension whereupon the
logger attribute of the Sigar class is marked for GC cleanup even if it
was never set. There is a GitHub issue for this bug here:
hyperic/sigar#28
pjulien
pushed a commit
to pjulien/sigar
that referenced
this issue
May 14, 2016
At the following line the
rb_sigar_mark
call back doesn't check whether logger is pointing to a valid Ruby object or not.sigar/bindings/ruby/rbsigar.c
Line 158 in 91aead2
The following ruby code will segfault without the sigar.logger set:
The text was updated successfully, but these errors were encountered: