Opened 13 years ago

Last modified 4 years ago

#624 new task (None)

Program location for thread error messages

Reported by: chak Owned by:
Priority: normal Milestone:
Component: Compiler Version: None
Keywords: Cc: ezyang@…
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Difficulty: Moderate (less than a day)
Test Case: Blocked By:
Blocking: Related Tickets:

Description (last modified by simonmar)

In programs with a substantial number of threads, the error messages like "indefinitely blocked" are not very helpful, because there is no indication as to which thread blocked. Having the source location of the 'fork' or so, would be much more helpful.

Change History (8)

comment:1 Changed 8 years ago by simonmar

  • Architecture set to Unknown
  • Description modified (diff)
  • Difficulty set to Moderate (1 day)
  • Operating System set to Unknown

comment:2 Changed 8 years ago by igloo

  • Milestone set to 6.6.1

comment:3 Changed 7 years ago by simonmar

  • Milestone changed from 6.6.1 to _|_

comment:4 Changed 6 years ago by simonmar

  • Architecture changed from Unknown to Unknown/Multiple

comment:5 Changed 6 years ago by simonmar

  • Operating System changed from Unknown to Unknown/Multiple

comment:6 Changed 4 years ago by simonmar

  • Difficulty changed from Moderate (1 day) to Moderate (less than a day)

comment:7 Changed 4 years ago by ezyang

  • Type of failure set to None/Unknown

It sounds like it would be pretty easy to add the thread identifier (indeed, you can already get that info if you compile with -debug and enable RTS tracing with +RTS -D, look for the "resurrecting thread" message). Source code identifier sounds a little bit tougher though; does GHC even let us do that without making forkIO inlined?

comment:8 Changed 4 years ago by ezyang

  • Cc ezyang@… added
Note: See TracTickets for help on using tickets.