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

Florian Pelz pelzflorian at googlemail.com
Tue Jun 9 13:26:03 UTC 2015

On 06/09/2015 09:26 AM, Oon-Ee Ng wrote:
> 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.


Have you read [1]? Also, tell the developers how to reproduce the bug
and since which version the bug occurs. You can pacman -U
/var/cache/pacman/pkg/<old-package> to install the old version again.

[1] https://wiki.archlinux.org/index.php/Step_By_Step_Debugging_Guide

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20150609/f5703d07/attachment.asc>

More information about the arch-general mailing list