[mercury-users] Profiling problems with mercury

[Fergus Henderson]

On 27-Apr-2004, Peter Hawkins <peter at hawkins.emu.id.au> wrote:
> I'm interested in using deep profiling. However, when I build my code using 
> GRADEFLAGS=--deep-profiling, the following happens on termination of my 
> program:
> *** Mercury runtime: caught segmentation violation ***
> PC at signal: 137140667 (82c99bb)
> address involved: 0xa8b9
> This may have been caused by a stack overflow, due to unbounded recursion.
> exiting from signal handler
> 
> Is deep profiling broken?

Yes.

> I am also unable to use mprof -c:
> $ mprof -c test_program
> Uncaught Mercury exception:
> Software Error: relation__lookup_element
> Stack dump not available in this grade.

This indicates a bug in the profiler.

This sort of thing usually happens because someone broke name mangling
or demangling.  The profiler is rather sensitive to the name mangling
algorithm, e.g. it will run into problems if two distinct symbols map
to the same demangled name.

-- 
Fergus Henderson                    |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-users mailing list
post:  mercury-users at cs.mu.oz.au
administrative address: owner-mercury-users at cs.mu.oz.au
unsubscribe: Address: mercury-users-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-users-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------