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

Florian Pelz pelzflorian at googlemail.com
Wed Jun 10 06:59:17 UTC 2015

On 06/10/2015 01:43 AM, Oon-Ee Ng wrote:
> On Tue, Jun 9, 2015 at 9:26 PM, Florian Pelz <pelzflorian at googlemail.com> wrote:
>> 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.
>> Hi,
>> 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
> Yes I have. Does not help as I do not know what is really causing the
> crash (as in, which update). The library was not updated, nor are
> there any missing dependencies or linked libraries (checked with ldd).

Have you tried running the application or the library's sample
application with gdb as described on the wiki? This way you would get
the exact place where it crashes. For more precise output (i.e. line
numbers in the source code), you might have to adapt the PKGBUILD as
described in [1]. Since the library and application are from the AUR,
you won't need ABS to get the PKGBUILD.


-------------- 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/20150610/50542018/attachment.asc>

More information about the arch-general mailing list