Bugs item #1041650, was opened at 2004-10-06 18:23
Message generated for change (Comment added) made by simonmar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1041650&group_id=8032

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: ghci failure with darcs

Initial Comment:
I tried to load some modules from darcs into ghci. 
Here is a mailing list post describing my problems:

http://www.abridgegame.org/pipermail/darcs-users/2004-October/003359.html

The first problem (libpthread), according to someone
else on the list, is a known issue with ghci.  (I tried
some hacks to work around it, described in later
messages, but hit other problems.)  The second problem
(unknown symbol `__stginit_SignalHandler_') seems to be
independent of the first, and I'm hoping is a simple
bug.  (The expression I'm trying to evaluate compiles
and runs fine with ghc.)

You should be able to reproduce the problem by
downloading the latest darcs sources, building, and
running the commands from my message.  I am running
Debian testing, with ghc6 package version  6.2.1-5.

----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2004-10-11 11:51

Message:
Logged In: YES 
user_id=48280

Bug closed, at request of submitter.

----------------------------------------------------------------------

Comment By: Andrew Pimlott (pimlott)
Date: 2004-10-08 22:05

Message:
Logged In: YES 
user_id=498741

Just putting my ID in the log.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2004-10-08 22:04

Message:
Logged In: NO 

If you follow the thread to

http://www.abridgegame.org/pipermail/darcs-users/2004-October/003443.html

you'll see that the second problem went away after a
recompile.  I don't know exactly what might have been stale,
because darcs linked and ran just fine.  But you can
probably close this bug.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1041650&group_id=8032
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to