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

Peter Wang wangp at students.csse.unimelb.edu.au
Wed Jan 3 14:02:42 AEDT 2007


On 2007-01-02, Ondrej Bojar <obo at cuni.cz> wrote:
> Hi and Happy New Year to everyone.
> 
> So the deep profiler problem is indeed caused by missing calls to 
> initialization (and finalization) procedures of modules that come from a 
> custom library. And the error was of mine.
> 
> I did not know that I must include --init-file flag for main program 
> compilation,

I didn't know that either.  Not too nice.

> For those interested, a working testcase is included to demonstrate 
> both: using an 'installed' and 'non-installed' library. In the testcase 
> directory type either 'make testinst' or 'make testnoninst'. In either 
> case, the library 'mylib' is prepared and the program 'mylib' is 
> compiled in asm_fast.gc.profdeep grade. See the main Makefile for the 
> two options of correct linking against the library.

I've just made a change that adds the correct --init-file-directory
option so you can pass "--init-file mylib.init", i.e. without the
directory component.

Peter

--------------------------------------------------------------------------
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