public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "swagiaal at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4256] Monitor library calls as well as system calls
Date: Thu, 22 Mar 2007 17:56:00 -0000	[thread overview]
Message-ID: <20070322175632.14319.qmail@sourceware.org> (raw)
In-Reply-To: <20070322145908.4256.fkung@redhat.com>


------- Additional Comments From swagiaal at redhat dot com  2007-03-22 17:56 -------
Yes. This is definatly a vaid functionality. One way we plan to address this is
through something called tag sets. Basically you instrument your souce code, or
the source code of a library with check points. These check points then cause
the monitor to draw events when they are reached during execution.

People can then share TagSets for library foo.so.

Anyone have any other ways for monitoring library calls ?.. is a library call
any different from a regular function call after the library has been loaded ?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |swagiaal at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4256

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


  reply	other threads:[~2007-03-22 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 14:59 [Bug general/4256] New: " fkung at redhat dot com
2007-03-22 17:56 ` swagiaal at redhat dot com [this message]
2007-03-22 18:03 ` [Bug general/4256] " cagney at redhat dot com
2007-03-22 19:32 ` swagiaal at redhat dot com

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=20070322175632.14319.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /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).