This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: About hacking libc
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Xinyang Ge <xxg113 at cse dot psu dot edu>
- Cc: Ángel González <keisial at gmail dot com>, libc-help at sourceware dot org
- Date: Mon, 17 Jun 2013 14:39:03 -0400
- Subject: Re: About hacking libc
- References: <CACY857JO7HoMRQyX1sb1gqR0DzK0PksBy0OPd7awCVbBSVKCPQ at mail dot gmail dot com> <CAE2sS1hv8CU45snKVOSzqYv-J9f4GcVp6v8GyAEg93cSQ=NWow at mail dot gmail dot com> <517EF6C4 dot 5040001 at gmail dot com> <CACY857+juSev+G6GQQdW6L5S4LF+9TWLSD27XDBLYsQz4xCuEg at mail dot gmail dot com>
On Mon, Jun 17, 2013 at 10:33 AM, Xinyang Ge <xxg113@cse.psu.edu> wrote:
> Thanks all. Does anyone know if there is a unified way to catch up all
> open-like library calls?
Define "all"? All libraries calls from the user's application or all
open calls including those from inside the library?
If the former, yes, just preload a shared library.
If the latter, no, but possible with something like System Tap.
I would be more than happy to see someone work on userspace system tap
probe points for all syscalls.
Such a probe point would catch everything from within the library in a
unified way.
Cheers,
Carlos.