Re: [Rpm-maint] [rpm-software-management/rpm] Bounds check strings to print correctly in %trace mode. (#160)

2017-02-24 Thread Florian Festi
Closed #160. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/160#event-975961542___ Rpm-maint mailing list

Re: [Rpm-maint] [rpm-software-management/rpm] Bounds check strings to print correctly in %trace mode. (#160)

2017-02-24 Thread Florian Festi
Added as part of #161 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/160#issuecomment-282279690___ Rpm-maint mailing list

Re: [Rpm-maint] [rpm-software-management/rpm] Bounds check strings to print correctly in %trace mode. (#160)

2017-02-20 Thread Peter Jones
It's not completely clear to me why the Jenkins check here failed, but it looks like it has to do with Jenkins, not with this patch. Given that https://github.com/rpm-software-management/rpm/pull/161 worked, I think this is fine. -- You are receiving this because you are subscribed to this

[Rpm-maint] [rpm-software-management/rpm] Bounds check strings to print correctly in %trace mode. (#160)

2017-02-20 Thread Peter Jones
In %trace mode, evaluating a macro which is undefined causes an invalid read of 1 byte when searching for the end of the string: trillian:~$ valgrind rpmspec --eval '%trace' --eval '%{?myUndefinedMacro}' ==21534== Memcheck, a memory error detector ==21534== Copyright (C) 2002-2015, and GNU GPL'd,