From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14361 invoked by alias); 22 Mar 2007 17:56:42 -0000 Received: (qmail 14320 invoked by uid 48); 22 Mar 2007 17:56:32 -0000 Date: Thu, 22 Mar 2007 17:56:00 -0000 Message-ID: <20070322175632.14319.qmail@sourceware.org> From: "swagiaal at redhat dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070322145908.4256.fkung@redhat.com> References: <20070322145908.4256.fkung@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4256] Monitor library calls as well as system calls X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00791.txt.bz2 List-Id: ------- 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.