[arch-general] Debugging third-party library's segfault if its caused by system update?

Oon-Ee Ng ngoonee.talk at gmail.com
Tue Jun 16 04:33:02 UTC 2015

On Tue, Jun 9, 2015 at 3:26 PM, Oon-Ee Ng <ngoonee.talk at gmail.com> wrote:
> I use the openni2 library to access an Asus Xtion Pro Live camera,
> installed from the AUR and working fine up till 2+ weeks ago.
> After a 2 week holiday, the most recent system update caused segfaults
> to happen within the library (both before and after rebuilding it),
> without any change to the code calling the library. Same segfault
> happens with the simple sample applications included in the library
> (previously running fine).
> How do I track down the issue? The library's source code is available,
> but without knowing it well I'm unsure where to even begin.
> Normally I'd contact the authors, but as this issue was caused (on my
> system) by a system update I think I'd need to do some tracking down
> first.

Dear all,

This is becoming curiouser and curiouser. Used the Arch Rollback
Machine to repeat the upgrades (without [testing]) and got all the way
till today without the problem reoccuring. Some more selective
upgrading revealed the problem to be libsystemd, systemd, and
systemd-sysvcompat (upgrading from 219-6 to 220-1 brings the problem
back reliably).

I am reporting this at https://bugs.archlinux.org/task/45343

More information about the arch-general mailing list