[pooma-dev] Profiling POOMA: How to? (1/3)

[Gabriel Dos Reis]

James Crotinger <JimC at proximation.com> writes:

[...]

| > III) Producing profiling information.
| > 
| >   To produce the actual profiling information, you have to invoke
| > gprof and the program being profiled as its argument.  Since gprof
| > writes directly on the standard output, you might want to use a
| > redirection :
| > 
| >    gprof atest > atest-pooma.prof
| 
| When I do this on my linux box (with ABCTest), gprof goes away for a very
| long time and then core dumps (after printing a message about not being able
| to allocate several gigabytes of memory). Any ideas? Is this related to your
| caveat? 

Hmm, I'm embarrased because I don't (yet) have any idea of why you're
seeing that behaviour.  Which parameters did you run the ABC
test with?  I tried the following to see whether I'll get a core dump

	./ABC --run-impls 2 --sim-params 1 3 100

and the test completed fine, but I strongly suspect I must be testing
with the wrong parameters (the "nan" part is a bit intriguing).  The
output is in ABC.out and the profiling information (flat profile and
call graph) is in ABC.prof, all attached.

I'm using GNU gprof-2.10.91 on a linux box.

Thanks,

-- Gaby

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ABC.out
Type: application/octet-stream
Size: 25295 bytes
Desc: not available
URL: <http://sourcerytools.com/pipermail/pooma-dev/attachments/20010824/517ca2f2/attachment.obj>
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ABC.prof
Type: application/octet-stream
Size: 24894 bytes
Desc: not available
URL: <http://sourcerytools.com/pipermail/pooma-dev/attachments/20010824/517ca2f2/attachment-0001.obj>