This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: print_backtrace not printing full stack

From: Mike Mason <mmlnx at us dot ibm dot com>
To: Jim Keniston <jkenisto at us dot ibm dot com>
Cc: "Frank Ch. Eigler" <fche at redhat dot com>, SystemTAP <systemtap at sources dot redhat dot com>
Date: Thu, 10 Aug 2006 15:31:50 -0700
Subject: Re: print_backtrace not printing full stack
References: <44DB8A6E.5000601@us.ibm.com> <y0mmzacwc9p.fsf@ton.toronto.redhat.com> <1155248580.3005.29.camel@localhost.localdomain>

Jim Keniston wrote:

On Thu, 2006-08-10 at 13:45, Frank Ch. Eigler wrote:

We also
know that kretprobes did or does have problems with corrupting
backtraces for even plain nested kernel-side probes.


Still does.  You'll see "kretprobe_trampoline" in the stack trace
wherever kretprobes has hijacked the return address of a kretprobed
function.  (The stack trace is not otherwise corrupted, to my
knowledge.)

I can live with kretprobe_trampoline in the stack trace of a return probe. The problem is that's all I'm seeing :-)

Mike

References:
- print_backtrace not printing full stack
  - From: Mike Mason
- Re: print_backtrace not printing full stack
  - From: Frank Ch. Eigler
- Re: print_backtrace not printing full stack
  - From: Jim Keniston

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]