#2087: On a PPC Mac OS X 10.4, the RTS reports "Memory leak detected" running a
program compiled with -debug -threaded -fhpc
----------------------------+-----------------------------------------------
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Runtime System | Version: 6.9
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: powerpc
Os: MacOS X |
----------------------------+-----------------------------------------------
Changes (by simonmar):
* difficulty: => Unknown
Comment:
Memory leaks are easy to detect, and hard to diagnose, sadly :(
I would start like this:
* find the smallest (shortest-running) program that displays the bug
* run it with `+RTS -DSbg -Sstderr` (sanity checking and block-alloc-
debugging)
If you really have a memory leak and not some free-list corruption or
something else, then the aim is to find who allocated the block that
leaked. Since you only have a very few blocks being allocated by the
program, it should be too hard to check them all - set a breakpoint on
allocGroup().
Is this happening on HEAD only, or 6.8.x too? (not sure which milestone to
add it to)
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2087#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
