This is the mail archive of the frysk-bugzilla@sourceware.org mailing list for the frysk 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]

[Bug general/4256] Monitor library calls as well as system calls


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


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