#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull | Owner: tibbe
Type: bug | Status: new
Priority: high
#7208: ghci panic: nameModule show{tv a9W}
--+-
Reporter: felipe zapata |Owner:
Type: bug| Status: closed
Priority: normal
#7208: ghci panic: nameModule show{tv a9W}
---+
Reporter: felipe zapata | Owner:
Type: bug| Status: new
Priority: normal
#7208: ghci panic: nameModule show{tv a9W}
---+
Reporter: felipe zapata | Owner:
Type: bug| Status: new
Priority: normal
#7208: ghci panic: nameModule show{tv a9W}
---+
Reporter: felipe zapata | Owner:
Type: bug| Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull | Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull | Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull | Owner: tibbe
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner: tibbe
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner: igloo
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: high
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
---+
Reporter: patrikja | Owner:
Type: bug | Status: closed
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
-+--
Reporter: patrikja |Owner:
Type: bug | Status: new
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
-+--
Reporter: patrikja |Owner:
Type: bug | Status: new
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
-+--
Reporter: patrikja |Owner:
Type: bug | Status: new
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
-+--
Reporter: patrikja |Owner:
Type: bug | Status: new
Priority: normal
#5268: ghci panic in ByteCodeGen.schemeE: unhandled case
-+--
Reporter: patrikja | Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
---+
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
-+--
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
-+--
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
-+--
Reporter: pturnbull |Owner:
Type: bug | Status: new
Priority: normal
#4245: ghci panic: thread blocked indefinitely in an MVar operation
--+-
Reporter: pturnbull |Owner:
Type: bug| Status: new
Priority: normal |Milestone
#4245: ghci panic: thread blocked indefinitely in an MVar operation
--+-
Reporter: pturnbull |Owner:
Type: bug| Status: new
Priority: high |Milestone
#4245: ghci panic: thread blocked indefinitely in an MVar operation
--+-
Reporter: pturnbull |Owner:
Type: bug| Status: new
Priority: normal |Milestone
#4245: ghci panic: thread blocked indefinitely in an MVar operation
--+-
Reporter: pturnbull | Owner:
Type: bug| Status: new
Priority: normal | Component: GHCi
#3839: ghci panic reading pragmas
--+-
Reporter: guest | Owner:
Type: bug| Status: closed
Priority: normal
#2113: +++ ghci panic
-+--
Reporter: guest| Owner:
Type: bug | Status: closed
Priority: normal | Milestone:
Component: GHCi |Version: 6.6.1
#2113: +++ ghci panic
---+
Reporter: guest |Owner:
Type: bug | Status: new
Priority: normal |Milestone:
Component: GHCi| Version: 6.6.1
#2113: +++ ghci panic
---+
Reporter: guest | Owner:
Type: bug | Status: new
Priority: normal | Component: GHCi
Version: 6.6.1 |Severity: normal
;Resolution: Fixed
Priority: 5
Submitted By: Ben Lippmeier (lambintheloop)
Assigned to: Nobody/Anonymous (nobody)
Summary: GHCi panic bytecode vs object code -O2
Initial Comment:
Compiling some source files with ghc -fglasgow-exts -O2
and some with GHCi results in GHCi panic. No FFI used
in sou
Status: Open
Resolution: None
Priority: 5
Submitted By: Ben Lippmeier (lambintheloop)
Assigned to: Nobody/Anonymous (nobody)
Summary: GHCi panic bytecode vs object code -O2
Initial Comment:
Compiling some source files with ghc -fglasgow-exts -O2
and some with GHCi results in GHCi panic. No FFI used
in
Yes, Sigbjorn is of course right. Disregard my msg ...
J
| > Did you bootstrap using itself?
|
| no, that is the pb. Sigbjorn Finne gave the explaination:
|
| > > GHCi doesn't load the RTS package (nor GMP),
| > > as they're both baked into the binary. My guess is that
| > > you've built ghc
"Julian Seward (Intl Vendor)" <[EMAIL PROTECTED]> writes:
> > % ghci
> > [...]
> > Loading package std ... linking ...
> > /usr/lib/ghc-5.02.2/HSstd.o: unknown symbol `stg_gc_l1'
> > ghc-5.02.2: panic! (the `impossible' happened, GHC version 5.02.2):
> > can't load package `std'
> > [...
Sent: Saturday, January 26, 2002 4:07 PM
| To: [EMAIL PROTECTED]
| Subject: ghci panic (unknown symbol stg_gc_l1)
|
|
| % ghci
| [...]
| Loading package std ... linking ...
| /usr/lib/ghc-5.02.2/HSstd.o: unknown symbol `stg_gc_l1'
| ghc-5.02.2: panic! (the `impossible' happened, GHC
"Sigbjorn Finne" <[EMAIL PROTECTED]> writes:
> GHCi doesn't load the RTS package (nor GMP),
> as they're both baked into the binary. My guess is that
> you've built ghci using 5.02.1; you need to use 5.02.2
> (i.e., do two stage build.) The missing symbol was
> introduced in 5.02.2's RTS.
cool,
l Message -
From: "Pixel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 26, 2002 08:07
Subject: ghci panic (unknown symbol stg_gc_l1)
> % ghci
> [...]
> Loading package std ... linking ... /usr/lib/ghc-5.02.2/HSstd.o: unknown
symbol `stg_gc_l1
% ghci
[...]
Loading package std ... linking ... /usr/lib/ghc-5.02.2/HSstd.o: unknown symbol
`stg_gc_l1'
ghc-5.02.2: panic! (the `impossible' happened, GHC version 5.02.2):
can't load package `std'
[...]
(it seems) it should load package "rts" before "std", but (it seems) it doesn't:
Hi Sigbjorn,
Thanks for the speedy reply!
Sigbjorn Finne wrote:
> "Antony Courtney" <[EMAIL PROTECTED]> writes:
>
> ...
>
>>Skipping HavenTest( HavenTest.hs, ./HavenTest.o )
>>PEi386 object has suspiciously large string table; > 64k relocs?
>>ghc.exe: panic! (the `impossible' happen
"Antony Courtney" <[EMAIL PROTECTED]> writes:
>
...
> Skipping HavenTest( HavenTest.hs, ./HavenTest.o )
> PEi386 object has suspiciously large string table; > 64k relocs?
> ghc.exe: panic! (the `impossible' happened, GHC version 5.02.1):
> loadObj: failed
>
Hi,
this is a known
Hi,
I got the following panic message when trying to load haven into ghci,
and the panic message said that I should report the problem, so here you
go. :)
I am using ghc 5.02.1 under Windows 2000 / Cygwin.
I'd really like to be able to use ghci for Haven development, so any
ideas on what mig
ghci -iutil:events -syslib lang -syslib data -syslibconcurrent util/object.o
[ lots of stuff skipped ]
Events> :load GuardedEvents
unloadObj: can't find `events/Events.o' to unload
ghc-5.00.2: panic! (the `impossible' happened, GHC version 5.00.2):
unloadObj: failed
Please report it as
51 matches
Mail list logo