On Tue, 2010-08-10 at 10:26 +0100, Dave Martin wrote:
> On Tue, Aug 10, 2010 at 10:16 AM, Loïc Minier wrote:
> > On Mon, Aug 09, 2010, John Rigby wrote:
> >> Does ltrace do what you want?
> >
> > This is what comes to my mind as well.
> >
> > There is a catch: I think eglibc (in fact almost all
On Tue, Aug 10, 2010 at 10:16 AM, Loïc Minier wrote:
> On Mon, Aug 09, 2010, John Rigby wrote:
>> Does ltrace do what you want?
>
> This is what comes to my mind as well.
>
> There is a catch: I think eglibc (in fact almost all Ubuntu packages)
> is built with -Bsymbolic-functions, which means
On Mon, Aug 09, 2010, John Rigby wrote:
> Does ltrace do what you want?
This is what comes to my mind as well.
There is a catch: I think eglibc (in fact almost all Ubuntu packages)
is built with -Bsymbolic-functions, which means that you can't
intercept internal calls to memcpy() from other e
>> Does anyone know of existing research with this information, or
>> existing tools that could capture it?
>
> The obvious answer is to rebuild both firefox and libc with -pg.
>
> Maybe Ubuntu already has a glibc package build for profiling?
Yip, but I want the arguments as well so we can tell wh
On Tue, Aug 10, 2010 at 9:21 AM, Andrew Stubbs wrote:
[...]
> The obvious answer is to rebuild both firefox and libc with -pg.
>
> Maybe Ubuntu already has a glibc package build for profiling?
I believe there may be a profiling C library already in the archive,
but most other libraries won't ha
Hi
> On Mon, Aug 9, 2010 at 8:47 PM, Michael Hope wrote:
>> I'd like to record the running of a typical program such as Firefox,
>> GCC, or ffmpeg and capture the calls and arguments to functions like
>> strcpy() and memcpy(). The idea is to generate a usage profile so we
>> can tell what standa
On Tue, 2010-08-10 at 14:47 +1200, Michael Hope wrote:
> I'd like to record the running of a typical program such as Firefox,
> GCC, or ffmpeg and capture the calls and arguments to functions like
> strcpy() and memcpy(). The idea is to generate a usage profile so we
> can tell what standard libr
On 10/08/10 03:47, Michael Hope wrote:
> I'd like to record the running of a typical program such as Firefox,
> GCC, or ffmpeg and capture the calls and arguments to functions like
> strcpy() and memcpy(). The idea is to generate a usage profile so we
> can tell what standard library functions and
Does ltrace do what you want?
On Mon, Aug 9, 2010 at 8:47 PM, Michael Hope wrote:
> I'd like to record the running of a typical program such as Firefox,
> GCC, or ffmpeg and capture the calls and arguments to functions like
> strcpy() and memcpy(). The idea is to generate a usage profile so we
>
Michael Hope wrote:
> I'd like to record the running of a typical program such as Firefox,
> GCC, or ffmpeg and capture the calls and arguments to functions like
> strcpy() and memcpy(). The idea is to generate a usage profile so we
> can tell what standard library functions and what variants (i.e
Will Oprofile help you on that?
BR,
Jason
> -Original Message-
> From: linaro-dev-boun...@lists.linaro.org
> [mailto:linaro-dev-boun...@lists.linaro.org] On Behalf Of Michael Hope
> Sent: Monday, August 09, 2010 10:47 PM
> To: linaro-dev@lists.linaro.org
> Subjec
I'd like to record the running of a typical program such as Firefox,
GCC, or ffmpeg and capture the calls and arguments to functions like
strcpy() and memcpy(). The idea is to generate a usage profile so we
can tell what standard library functions and what variants (i.e.
aligned/unaligned, small c
12 matches
Mail list logo
