[PATCH 2/2] unwind: relax the pass condition of strace-k.test test case
yamato at redhat.com
Tue Jun 17 03:25:36 UTC 2014
On Tue, 17 Jun 2014 04:16:27 +0400, "Dmitry V. Levin" <ldv at altlinux.org> wrote:
> On Mon, Jun 16, 2014 at 12:07:32PM +0900, Masatake YAMATO wrote:
>> How about x86_64?
>> I guess testing on x86_64 is failed, too.
> No, on x86_64 the test always succeeds.
> On armv7hl it is unreliable: sometimes it succeeds
> (e.g. https://koji.fedoraproject.org/koji/taskinfo?taskID=7043723),
> sometimes it fails
> (e.g. https://koji.fedoraproject.org/koji/taskinfo?taskID=7049221),
> and on my local armv7hl host it always fails with "too many stack frames".
>> It seems that the libunwind on fedora is not linked to liblzma.
>> As the result it cannot decode minidebug info.
> This is not necessarily the root of all problems.
>> As far as trying with privately built libunwind f1, f0 and main are
>> decoded expectedly.
>> BTW, I'm afraid stack-fcall used in the test is more optimized than I
> No, stack-fcall is not overoptimized. I've split stack-fcall.c into several
> compilation units just to be sure that intermediate function calls are not
> optimized out (see https://sourceforge.net/p/strace/code/ci/ldv/unwind/~/log/)
> and made another test build:
> You can see that on x86_64 the test succeeded, and on i686 and armv7hl it
However, I want the i686 binary of test case anyway to inspect at
More information about the Strace-devel