[mercury-users] Deep profiler data corrupted: unwritten nodes

Zoltan Somogyi zs at csse.unimelb.edu.au
Fri Dec 22 16:20:38 AEDT 2006

On 22-Dec-2006, Ondrej Bojar <obo at cuni.cz> wrote:
> Julien Fischer wrote:
> >It's more likely that in this case the profiling interrupt turned up
> >while the program was executing some C code.
> The same issue appeared in with a program with very limited or maybe 
> none C code, but I would need to double check to be sure.
> But in case there is a significant portion of C code used in my app, it 
> is very likely that the profiling interrupt would strike at a wrong 
> point. Deep profiling is not usable for such situations?

Deep profiling is usable, but of course it won't tell you which part of
the C code you spend your time in.

> The _init.c file for my program indeed does not contain any calls to 
> save deep profiler data for my libtools modules. (But it contains such 
> calls for mercury standard library modules, though.)

That would be the problem.

> In fact, I am surprised to see no _init.c files in the 
> tools/obomerclib/Mercury/<grade>/ at all. So there are no _init.c files 
> generated for the library modules?

No. The installed system should have .init files in the grade-specific
directories. Each program's _init.c file is derived (in part) from these files.

mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list