[PATCH 2/2] unwind: relax the pass condition of strace-k.test test case

[Masatake YAMATO]

How about x86_64?

I guess testing on x86_64 is failed, too.

It seems that the libunwind on fedora is not linked to liblzma. 
As the result it cannot decode minidebug info.

   https://bugzilla.redhat.com/show_bug.cgi?id=972737

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
expected. Could you send me the binary to me privately? 

Masatake YAMATO


On Fri, 13 Jun 2014 20:25:22 +0400, "Dmitry V. Levin" <ldv at altlinux.org> wrote:
> On Thu, Jun 12, 2014 at 03:44:54AM +0900, Masatake YAMATO wrote:
>> strace-k.test is failed on i386 GNU/Linux. I inspect the reason and it
>> seems that libunwind does not have enough ability to unwinding the
>> stack when pc is at [vdso].  However, I think stacktrace feature is
>> still useful even on i386 GNU/Linux. So this patch relaxes the pass
>> condition of strace-k.test test case.
> 
> Unfortunately, this relaxation seems to be insufficient.
> The only x86 GNU/Linux instance I've seen where strace-k.test fails is
> i686 Fedora rawhide:
> 
> https://kojipkgs.fedoraproject.org/work/tasks/3725/7043725/build.log
> (built from https://sourceforge.net/p/strace/code/ci/ldv/unwind/~/log/)
> 
> tests$ ../strace -e getpid -k ./stack-fcall
> getpid()                                = 3372
>  > [vdso](+0x0) [0x430]
>  > /usr/lib/libc-2.19.90.so(__libc_start_main+0xde) [0x17e8e]
>  > /builddir/build/BUILD/strace-4.9/tests/stack-fcall(_start+0x21) [0x35c]
> +++ exited with 0 +++
> 
> 
> -- 
> ldv