Date: Mon, 18 Mar 2019 13:33:30 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 214338] [PATCH] devel/glib20: new kqueue() backend for file monitoring Message-ID: <bug-214338-6497-rjPqf3AwLZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214338-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-214338-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214338 --- Comment #73 from Ting-Wei Lan <lantw44@gmail.com> --- (In reply to rozhuk.im from comment #70) Can you type 'disassemble' in GDB and paste the output? Seeing illegal instruction error without knowing which instruction causes the error isn't = very useful because the backtrace isn't related to the file monitor. I don't claim that GLib port shipped with FreeBSD doesn't have problems. In fact, I know it has problems and I modified hundreds of lines of GLib code = in the kqueue file monitor backend during the 2.58 cycle. This includes fixes = for crashes caused by race conditions in order to let GLib pass all tests on FreeBSD and run tests regularly on the upstream CI. It will be nice if you = can test the latest version of GLib (currently 2.60) instead of the outdated version included in FreeBSD ports to know whether upstream GLib still has problems. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214338-6497-rjPqf3AwLZ>