Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 179558 - dev-lang/ghc-6.4.2 --interactive segfaults when calling 'getEnvironment'
Summary: dev-lang/ghc-6.4.2 --interactive segfaults when calling 'getEnvironment'
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo's Haskell Language team
URL:
Whiteboard:
Keywords:
: 179561 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-05-23 18:20 UTC by gustavderdrache
Modified: 2007-07-11 13:48 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gustavderdrache 2007-05-23 18:20:02 UTC
When using ghci to load the System.Environment module and subsequently calling "getEnvironment" at the command line, ghci segfaults.  Other functions in the module work correctly, but calling "getEnvironment" at any time will cause it to crash.

Reproducible: Always

Steps to Reproduce:
1. Start ghci
2. Enter ":m System.Environment"
3. Enter "getEnvironment"

Actual Results:  
ghci segfaults

Expected Results:  
The special variable "it" in ghci's environment should be updated with the return value of getEnvironment (something like the following: [("DISPLAY", ":0.0"), ("SHELL", "/bin/bash")] )

The presence of other modules does not affect this bug; modules may be loaded before and after (or both) without altering its behavior.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-05-23 18:24:55 UTC
No idea whatsover what's ghci; reopen with exact ebuild and version.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-05-23 18:29:41 UTC
*** Bug 179561 has been marked as a duplicate of this bug. ***
Comment 3 gustavderdrache 2007-05-23 18:41:30 UTC
Reopened with ebuild name and version as noted in comment #1.
Comment 4 Duncan Coutts (RETIRED) gentoo-dev 2007-05-24 11:31:34 UTC
I can reproduce this on amd64 for ghc-6.4.2 and ghc-6.6.
I'll see if it's fixed in 6.6.1 or is known upstream.
Comment 5 Duncan Coutts (RETIRED) gentoo-dev 2007-05-30 20:50:08 UTC
This bug is recorded upstream: http://hackage.haskell.org/trac/ghc/ticket/781
Comment 6 Duncan Coutts (RETIRED) gentoo-dev 2007-07-11 13:48:13 UTC
We can't fix this one ourselves I'm afraid. We'll just have to wait for upstream to do it in some future release.