threadDelay not ending
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process. This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo. Any ideas? What would have changed between 6.4 and 6.4.2 that would cause this behavior? Thanks, Rich
What is your environment? My project (which is about 70% Haskell) makes extensive use of threadDelay. I've not seen this behavior with 6.4.2. My environment is Linux using a recent 2.6 kernel. For obvious reasons I need to know whether there is a threadDelay issue here that is preparing to bite me. Seth Kurtzberg On Mon, September 18, 2006 7:23 am, Rich Fought wrote:
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process.
This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo.
Any ideas? What would have changed between 6.4 and 6.4.2 that would cause this behavior?
Thanks, Rich
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
-- Seth Kurtzberg seth@cql.com Software Engineer Specializing in Reliability and Security
I am running on Red Hat Enterprise Linux with the latest RH 2.6 kernel. This is very bizarre and I am having a hard time figuring out what is going on. I don't see any issues in the project code itself, just my unit tests. Rich Seth Kurtzberg wrote:
What is your environment?
My project (which is about 70% Haskell) makes extensive use of threadDelay. I've not seen this behavior with 6.4.2. My environment is Linux using a recent 2.6 kernel.
For obvious reasons I need to know whether there is a threadDelay issue here that is preparing to bite me.
Seth Kurtzberg
On Mon, September 18, 2006 7:23 am, Rich Fought wrote:
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process.
This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo.
Any ideas? What would have changed between 6.4 and 6.4.2 that would cause this behavior?
Thanks, Rich
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
On Mon, 18 Sep 2006 11:56:21 -0500
Rich Fought
I am running on Red Hat Enterprise Linux with the latest RH 2.6 kernel.
This is very bizarre and I am having a hard time figuring out what is going on. I don't see any issues in the project code itself, just my unit tests.
Rich, I'm having trouble coming up with even a credible theory of what might be happening. I can't come up with any theory, no matter how far fetched, that would account for things working with 6.4.1 and not working with 6.4.2. If there is anything I can do to help you narrow this down, let me know. Seth
Rich
Seth Kurtzberg wrote:
What is your environment?
My project (which is about 70% Haskell) makes extensive use of threadDelay. I've not seen this behavior with 6.4.2. My environment is Linux using a recent 2.6 kernel.
For obvious reasons I need to know whether there is a threadDelay issue here that is preparing to bite me.
Seth Kurtzberg
On Mon, September 18, 2006 7:23 am, Rich Fought wrote:
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process.
This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo.
Any ideas? What would have changed between 6.4 and 6.4.2 that would cause this behavior?
Thanks, Rich
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Hello Seth, Tuesday, September 19, 2006, 3:35:54 AM, you wrote:
I'm having trouble coming up with even a credible theory of what might be happening. I can't come up with any theory, no matter how far fetched, that would account for things working with 6.4.1 and not working with 6.4.2.
one possible method is to download various builds dated between 6.4 and 6.4.2 and find exact one when program started to fail. afair, you can find prebuilt daily snapshots for Linux in the 'Download' section -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com
* Rich Fought
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process.
This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo.
You could build an RTS with debugging support to see what is going on. Volker
Hi Rich, On Mon, Sep 18, 2006 at 09:23:52AM -0500, Rich Fought wrote:
I've got some unit test code that forks off test processes using the 'system' function and then delays using 'threadDelay' to synchronize with the test process.
This has worked fine until I upgraded to 6.4.2, now some of the 'threadDelay' calls never return - it's like they are stuck in limbo.
Are you compiling with -threaded? Are you able to send us a small example demonstrating the problem? Thanks Ian
participants (5)
-
Bulat Ziganshin -
Ian Lynagh -
Rich Fought -
Seth Kurtzberg -
Volker Stolz