Re: memprof-0.5.1 revisited



I no longer maintain memprof. You might want to post this to the 
memprof mailing list.

http://mail.gnome.org/mailman/listinfo/memprof-list
 

Regards,
						Owen

On Mon, 2005-07-11 at 13:40 -0400, Joseph E. Sacco, PhD wrote:
> This is another attempt at hacking memprof-0.5.1 to run on a 32 bit PPC.
> Attached are files to implement the changes within GARNOME.
> 
> 
> Discussion
> -----------
> Three files were patched in order to get memprof to build, install, and
> run.
> 
> * bfdutils.c
> coding changes made because libbfd has changed since 2002
> 
> * memintercept-utils.c
> atomic operations taken from glibc to implement
> atomic_increment/decrement for platforms that uses glibc
> [Must have /usr/include/asm/atomic.h installed].
>  
> * stack-frame.c
> removed an __i386__ restriction and got away with it on a 32 bit PPC
> [maybe...]
> 
> 
> Observations
> -------------
> * I doubt this version of memprof will work on a 64 bit machine.
> 
> * The build generates a few warnings that appear to be unimportant on a
> 32 bit machine.
> 
> * running the application sometimes generates warnings about failure to
> access the very first element in a memory block. 
> 
> For example:
> 
>         ** (memprof:7657): WARNING **: Cannot read word 0/52 in block
>         0x1ffc18d4: Input/output error
>         
>         
>         ** (memprof:7657): WARNING **: Cannot read word 0/2444 in block
>         0x3fc577fc: Input/output error
>         
>         
>         ** (memprof:7657): WARNING **: Cannot read word 0/61 in block
>         0x3fc57000: Input/output error
> 
> 
> -Joseph
> 
-- 
Owen Taylor <otaylor redhat com>

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]