On 10/04/2017 06:59 PM, Thierry Vignaud wrote:
On 4 October 2017 at 14:17, Thierry Vignaud wrote:
Also this new rpm introduced segfault regressions in both RPM4 &
urpmi
testsuites
See attached gdb traces in BUG*.txt
valgrind seems to hint about invalid writes/reads
On 4 October 2017 at 17:59, Thierry Vignaud wrote:
> The urpmi issue is when checking bogus pkgs.
> The RPM4 issue is when traversing the transaction (not the rpmdb)
> Attached are the valgrind outputs
>
So we have stuff
On 4 October 2017 at 14:17, Thierry Vignaud wrote:
> Also this new rpm introduced segfault regressions in both RPM4 &
> urpmi
> testsuites
> See attached gdb traces in BUG*.txt
> valgrind seems to hint about invalid writes/reads
On 4 October 2017 at 13:26, Panu Matilainen wrote:
Also this new rpm introduced segfault regressions in both RPM4 &
urpmi
testsuites
See attached gdb traces in BUG*.txt
valgrind seems to hint about invalid writes/reads
See
On 10/04/2017 01:25 PM, Thierry Vignaud wrote:
On 3 October 2017 at 09:12, Panu Matilainen wrote:
Also this new rpm introduced segfault regressions in both RPM4 & urpmi
testsuites
See attached gdb traces in BUG*.txt
valgrind seems to hint about invalid writes/reads
See you
On 3 October 2017 at 09:12, Panu Matilainen wrote:
>> Also this new rpm introduced segfault regressions in both RPM4 & urpmi
>> testsuites
>> See attached gdb traces in BUG*.txt
>> valgrind seems to hint about invalid writes/reads
>> See you
>
>