timeout(1) allows you to specify the signal(7) sent with the --signal option. It may be worth experimenting with different values. One of them might terminate the program while allowing it to clean up and generate profiling information. I don't know enough about the haskell runtime to know. -vale -- vale cofer-shabica 401.267.8253 On Wed, May 4, 2016 at 7:06 PM, Tim Perry wrote:

I believe that timeout sends a kill signal to the process in question. I imagine that the process is killed before the profiling information is written and so you get an empty file. When you close the program with alt-F4, the program gets a chance to shut down cleanly and writes on the profiling information (.prof)

On Wed, May 4, 2016 at 9:11 AM, Ben Rogalski wrote:

...

I would like to generate a time and allocation profiling report after running my program for exactly 60 seconds (on Ubuntu Linux).

I compiled with the following flags:

-rtsopts -auto-all -caf-all -fforce-recomp

I then ran the program:

The program stops after 60 seconds, but the .prof file is empty.

When I run the program without using timeout, and close it manually (Alt F4, it is a graphical program), the .prof file contains the information I would expect.

_______________________________________________ Beginners mailing list Beginners@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners

_______________________________________________ Beginners mailing list Beginners@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners