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

Re: Track libc calls

From: Davide Italiano <davide dot italiano at gmail dot com>
To: libc-help at sourceware dot org
Date: Thu, 12 Aug 2010 15:53:09 +0200
Subject: Re: Track libc calls
References: <AANLkTi=YW3cbrhPKr9-oq1CSDrCLUYtpy=WsJZo-3rq6@mail.gmail.com><AANLkTimb7ZzErxJsov5MU2icyG5vtQ5R558MX9woJS4j@mail.gmail.com>

I was looking for a solution that doesn't use external tools

On Wed, Aug 11, 2010 at 9:25 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Wed, Aug 11, 2010 at 3:13 PM, Davide Italiano wrote:
>> So, my question is: Is there a sane way to do this?
>
> use gdb and set breakpoints on every function entry point
> -mike
>

Follow-Ups:
- Re: Track libc calls
  - From: Mike Frysinger

References:
- Track libc calls
  - From: Davide Italiano
- Re: Track libc calls
  - From: Mike Frysinger

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