
Apologies for the empty post.
You might turn your attention to the following web page, which approaches the problem using recursive co-routines. Amidst a discussion of UNIX pipes, both in history and as a primitive co-routine implementation, there is a two-line Haskell program.
http://www.cs.dartmouth.edu/~doug/sieve/
-----Original Message-----
From: "beginners-request@haskell.org"
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
participants (1)
-
Peter McIlroy