[Bug 226920] devel/glib20: pull the latest file monitor fix from upstream

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226920

--- Comment #15 from lightside <lightside at gmx.com> ---
Created attachment 192575
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192575&action=edit
Backtrace for x11-fm/caja (v1.20.2)

Attached some backtrace for x11-fm/caja (v1.20.2; with WITH_DEBUG=yes) on
FreeBSD 10.3 amd64.

Testcase was many opened caja windows for some port in user directory,
including for some directories in related work directory after `make
check-plist` command (which was launched from mate-terminal (v1.20.0;
x11/mate-terminal) window). The caja crashed (and caja.core file created inside
${HOME} directory) after `make clean` command. Also there was opened some text
editor (editors/scite) for Makefile (and probably some file(s) inside work
directory) before caja crash. Possible, that mate-terminal also was opened for
some work directory, but probably this is not related.

Previously I reproduced mentioned testcase (for attachment #191870) without
debug symbols. Then I tested with debug symbols (WITH_DEBUG=yes) for
devel/glib20 and x11-fm/caja (v1.18.4 and v1.20.2). But mentioned caja crash
was once after this (for which backtrace was attached). So, I accidentally
reproduced this testcase once more (i.e. it was rare).

Not sure, if my explanations about testcase and some programs before caja crash
was useful, but as is.

-- 
You are receiving this mail because:
You are on the CC list for the bug.