Re: Debugging third-party library's segfault if its caused by system update?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Tue, Jun 9, 2015 at 9:26 PM, Florian Pelz <pelzflorian@xxxxxxxxxxxxxx> 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).


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux