Re: [RFC] print stack trace after each syscall

2013-07-07 Thread Luca Clementi
On Wed, Jul 3, 2013 at 9:58 AM, Mike Frysinger wrote: > On Tuesday 02 July 2013 21:54:17 Luca Clementi wrote: >> Regarding PKG_CHECKS_MODULE I am not too convinced (although I must >> say that I am not an expert of autoconf). >> For example Ubuntu 12.04 the system libunwind7 and libunwind7-dev do

Re: [RFC] print stack trace after each syscall

2013-07-03 Thread Mike Frysinger
On Tuesday 02 July 2013 21:54:17 Luca Clementi wrote: > Regarding PKG_CHECKS_MODULE I am not too convinced (although I must > say that I am not an expert of autoconf). > For example Ubuntu 12.04 the system libunwind7 and libunwind7-dev do > not include the .pc files needed by PKG_CHECKS_MODULE. lo

Re: [RFC] print stack trace after each syscall

2013-07-02 Thread Luca Clementi
On Thu, Jun 27, 2013 at 10:41 PM, Mike Frysinger wrote: > On Tuesday 25 June 2013 02:41:21 Luca Clementi wrote: >> On Mon, Jun 24, 2013 at 8:42 AM, Mike Frysinger wrote: >> > On Monday 24 June 2013 03:18:58 Luca Clementi wrote: >> >> + AC_CHECK_LIB([unwind], [backtrace],[],[ >> >> +

Re: [RFC] print stack trace after each syscall

2013-06-27 Thread Mike Frysinger
On Tuesday 25 June 2013 02:41:21 Luca Clementi wrote: > On Mon, Jun 24, 2013 at 8:42 AM, Mike Frysinger wrote: > > On Monday 24 June 2013 03:18:58 Luca Clementi wrote: > >> + AC_CHECK_LIB([unwind], [backtrace],[],[ > >> + AC_MSG_FAILURE([Unable to find libunwind]) > >> +

Re: [RFC] print stack trace after each syscall

2013-06-26 Thread Dmitry V. Levin
On Mon, Jun 24, 2013 at 12:18:58AM -0700, Luca Clementi wrote: > This patch prints the stack trace of the traced process after > each system call when using -k flag. It uses libunwind to > unwind the stack and to obtain the function name pointed by > the IP. [...] > --- a/defs.h > +++ b/defs.h > @@

Re: [RFC] print stack trace after each syscall

2013-06-26 Thread Masatake YAMATO
> On Tue, Jun 25, 2013 at 7:08 AM, Masatake YAMATO wrote: >> Hi, >> >> I need following patch to avoid strace+ coredump. >> Could you merge it the official source tree? >> >> >> Signed-off-by: Masatake YAMATO >> >> diff --git a/syscall.c b/syscall.c >> index a569a65..1b8f613 100644 >> --- a/sysca

Re: [RFC] print stack trace after each syscall

2013-06-26 Thread Luca Clementi
On Tue, Jun 25, 2013 at 7:08 AM, Masatake YAMATO wrote: > Hi, > > I need following patch to avoid strace+ coredump. > Could you merge it the official source tree? > > > Signed-off-by: Masatake YAMATO > > diff --git a/syscall.c b/syscall.c > index a569a65..1b8f613 100644 > --- a/syscall.c > +++ b/

Re: [RFC] print stack trace after each syscall

2013-06-25 Thread Masatake YAMATO
(I've just joined this list. So I could not set Reply-to properly.) Here is a patch I sent to the strace+ developer. It seems that this is still applicable to Luca's new patch. Masatake YAMATO Hi, I need following patch to avo

Re: [RFC] print stack trace after each syscall

2013-06-25 Thread Luca Clementi
On Mon, Jun 24, 2013 at 3:44 AM, Denys Vlasenko wrote: > On 06/24/2013 09:18 AM, Luca Clementi wrote: > >> +void alloc_mmap_cache(struct tcb* tcp) { >> + >> + if ( tcp->mmap_cache) >> + perror_msg_and_die("Memory map cache is empty"); >> + if ( tcp->mmap_cache_size) >> +

Re: [RFC] print stack trace after each syscall

2013-06-24 Thread Luca Clementi
On Mon, Jun 24, 2013 at 8:42 AM, Mike Frysinger wrote: > On Monday 24 June 2013 03:18:58 Luca Clementi wrote: >> --- a/configure.ac >> +++ b/configure.ac >> >> +dnl libunwind tests >> +AC_CHECK_HEADERS([libunwind-ptrace.h libunwind.h]) > > add a proper --with/--enable flag for this. the default

Re: [RFC] print stack trace after each syscall

2013-06-24 Thread Mike Frysinger
On Monday 24 June 2013 03:18:58 Luca Clementi wrote: > --- a/configure.ac > +++ b/configure.ac > > +dnl libunwind tests > +AC_CHECK_HEADERS([libunwind-ptrace.h libunwind.h]) add a proper --with/--enable flag for this. the default should be to autodetect the headers and not fail if support isn'

Re: [RFC] print stack trace after each syscall

2013-06-24 Thread Denys Vlasenko
On 06/24/2013 09:18 AM, Luca Clementi wrote: > This patch prints the stack trace of the traced process after > each system call when using -k flag. It uses libunwind to > unwind the stack and to obtain the function name pointed by > the IP. > > Tested on Ubuntu 12.04 64 with the distribution versio