public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
* [Bug general/4256] New: Monitor library calls as well as system calls
@ 2007-03-22 14:59 fkung at redhat dot com
  2007-03-22 17:56 ` [Bug general/4256] " swagiaal at redhat dot com
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: fkung at redhat dot com @ 2007-03-22 14:59 UTC (permalink / raw)
  To: frysk-bugzilla

Rather than only showing system calls in the monitor, it would be a nice feature
to monitor library calls as well.  It would be an extremely useful supplement to
backtraces when debugging a problem.

To reduce verbosity, a filter can be added so that only calls into specified
libraries are logged.

-- 
           Summary: Monitor library calls as well as system calls
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: fkung 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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug general/4256] Monitor library calls as well as system calls
  2007-03-22 14:59 [Bug general/4256] New: Monitor library calls as well as system calls fkung at redhat dot com
@ 2007-03-22 17:56 ` swagiaal at redhat dot com
  2007-03-22 18:03 ` cagney at redhat dot com
  2007-03-22 19:32 ` swagiaal at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: swagiaal at redhat dot com @ 2007-03-22 17:56 UTC (permalink / raw)
  To: frysk-bugzilla


------- 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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug general/4256] Monitor library calls as well as system calls
  2007-03-22 14:59 [Bug general/4256] New: Monitor library calls as well as system calls fkung at redhat dot com
  2007-03-22 17:56 ` [Bug general/4256] " swagiaal at redhat dot com
@ 2007-03-22 18:03 ` cagney at redhat dot com
  2007-03-22 19:32 ` swagiaal at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: cagney at redhat dot com @ 2007-03-22 18:03 UTC (permalink / raw)
  To: frysk-bugzilla


------- Additional Comments From cagney at redhat dot com  2007-03-22 18:03 -------
> 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 ?

Identical.

(well sometimes its a call through a function pointer, and sometimes through a
"thunk").

-- 


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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug general/4256] Monitor library calls as well as system calls
  2007-03-22 14:59 [Bug general/4256] New: Monitor library calls as well as system calls fkung at redhat dot com
  2007-03-22 17:56 ` [Bug general/4256] " swagiaal at redhat dot com
  2007-03-22 18:03 ` cagney at redhat dot com
@ 2007-03-22 19:32 ` swagiaal at redhat dot com
  2 siblings, 0 replies; 4+ messages in thread
From: swagiaal at redhat dot com @ 2007-03-22 19:32 UTC (permalink / raw)
  To: frysk-bugzilla


------- Additional Comments From swagiaal at redhat dot com  2007-03-22 19:32 -------
This is done by ltrace (http://packages.debian.org/unstable/source/ltrace)
thanks to cagney for the pointer.

I couldnt quickly tell from the code but one possibility is that it monitors all
library loads then sets breakpoints on all the functions of a library as soon as
it is loaded.

-- 


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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-03-22 19:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-03-22 14:59 [Bug general/4256] New: Monitor library calls as well as system calls fkung at redhat dot com
2007-03-22 17:56 ` [Bug general/4256] " swagiaal at redhat dot com
2007-03-22 18:03 ` cagney at redhat dot com
2007-03-22 19:32 ` swagiaal at redhat dot com

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).