Frederik Eaton wrote:
No time to try to reproduce it, I'm preparing for a conference ;)
I haven't seen the bug recently, but ... tangentially I was musing
that if someone could devote some time to turning the GHC internal
error message (which I've seen on over a hundred occasions, I'm sure)
into a tool that queries the user and then, if he is OK with sharing
his code (as a quite large number of programmers are) sends a core
dump of GHC into some repository to be analysed, it might be
beneficial for the GHC development process in the long run. This
concept probably has a standard name that I don't know - I think
something vaguely similar was done with some web browsers once,
although perhaps not with the entire program state. It sounds like it
might be difficult to implement, though. Just a thought.
For some errors that would definitely be useful - e.g. for a GHC panic if there
was an option to send the source code back to us automatically, I'm sure that
would help us track down bugs more quickly. Unfortunately the crash you ran
into was in the runtime, and in my experience just looking at a snapshot of the
state at the point of the crash is unlikely to be revealing. I can very rarely
track down an RTS bug from just a core dump.
Still, I think the idea in principle is great - we want to make it easier for
people to package up all the information we need to repeat a bug.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
