[RFC] print stack trace after each syscall

[Mike Frysinger]

On Tuesday 25 June 2013 02:41:21 Luca Clementi wrote:
> On Mon, Jun 24, 2013 at 8:42 AM, Mike Frysinger <vapier at gentoo.org> wrote:
> > On Monday 24 June 2013 03:18:58 Luca Clementi wrote:
> >> +     AC_CHECK_LIB([unwind], [backtrace],[],[
> >> +             AC_MSG_FAILURE([Unable to find libunwind])
> >> +             ])
> >> +        AC_CHECK_LIB([unwind-$arch], [_U${arch}_create_addr_space],[],
> >> [ +                           AC_MSG_FAILURE([Unable to find
> >> libunwind-$arch]) +     ])
> > 
> > is the $arch stuff really necessary ?  isn't linking to -lunwind
> > sufficient ?
> 
> Actually what I do need is the libunwind-ptrace, but the problem is
> that -lunwind-ptrace depends on -lunwind-$arch (basically they put all
> the arch dependent code in there) so if you test libunwind-ptrace you
> need to have the -lunwind-$arch in your linker flags if not the test
> fails.

i think what you want is to use PKG_CHECK_MODULES and look up libunwind-
generic instead.  libunwind takes care of linking that to the right arch.
lrwxrwxrwx 1 root root    19 Nov  2  2012 /usr/lib64/libunwind-generic.so ->
	libunwind-x86_64.so
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20130628/86c5ed37/attachment.bin>