public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Bryce <philip.copeland@oracle.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Question on checking the stack
Date: Thu, 13 Oct 2005 15:58:00 -0000	[thread overview]
Message-ID: <434E8410.30703@oracle.com> (raw)
In-Reply-To: <y0mll0xbesd.fsf@toenail.toronto.redhat.com>

Frank Ch. Eigler wrote:

>Bryce <philip.copeland@oracle.com> writes:
>
>  
>
>>Setting up a probe for a function is great and all but is there a way
>>to test how we entered the routine?
>>[...]
>>    
>>
>
>Just about all the essentials are in there somewhere, just
>not in a convenient-to-use form.
>
>  
>
>>probe kernel.function("generic_make_request") {
>>    if (stack(1) == "submit_bio" ) { // where stack(1) was the last
>>routine  and stack(2) was 2nd last etc
>>         do_test/display
>>    }
>>}
>>    
>>
>
>The tapset/context.stp file would need two new functions such as these:
>
>  caller:string(n:long) - returns the nth substring as if from backtrace()
>  addr2symbol:string(n:long) - address-to-symbol lookup, which is exactly
>                               one stage of print_stack()
>
>- FChE
>  
>

*nod* Just Sebastiaens hack has the unfortunate problem of needing to 
know in advance what all the exit addresses from a routine and combing 
the stack looking for a string match is probably rather slow if it 
happens often enough.

Cheers

Phil
=--=


  reply	other threads:[~2005-10-13 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 10:44 Bryce
2005-10-13 15:46 ` Frank Ch. Eigler
2005-10-13 15:58   ` Bryce [this message]
2005-10-13 17:01     ` Frank Ch. Eigler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=434E8410.30703@oracle.com \
    --to=philip.copeland@oracle.com \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).