guarded-allocation: Memory allocation with added stress tests and integrity checks

[ bsd3, debug, library ] [ Propose Tags ]

Provide adaptions of mallocForeignPtrArray and allocaArray that add stress tests and integrity checks.

There are three modules:

It is intended that you always import the Guarded module in user code and install a package version with enabled debug flag to a custom package database for debugging. If you compile your user program you can choose production or debugging mode by choosing the default or the custom debugging package database, respectively.

This package is inspired by the famous Amiga debug tool MungWall. The Linux counterpart is Electric Fence.

[Skip to Readme]
Versions [RSS] [faq] 0.0, 0.0.1
Dependencies base (>=4.5 && <5) [details]
License BSD-3-Clause
Author Henning Thielemann <>
Maintainer Henning Thielemann <>
Category Debug
Home page
Source repo this: darcs get --tag 0.0.1
head: darcs get
Uploaded by HenningThielemann at 2019-01-22T11:45:24Z
Distributions LTSHaskell:0.0.1, NixOS:0.0.1, Stackage:0.0.1
Downloads 1638 total (15 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2019-01-22 [all 1 reports]


[Index] [Quick Jump]

Manual Flags


Add stress tests and integrity checks to allocations

Automatic Flags

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info


Maintainer's Corner

For package maintainers and hackage trustees


Readme for guarded-allocation-0.0.1

[back to package description]

The overall idea of the package is to make programming mistakes let low-level programs fail reproducibly.

What the routines do:

  • After allocation fill the memory with the hex string 0xDEADF00D. This allows to check whether the caller properly initialises allocated buffers.

  • Allocate some memory before and after the actual buffer and fill it with 0xABADCAFE. On deallocation it is checked that this pattern is still intact. If not, abort with an error. This allows to check for range violations.

  • Before deallocation fill the memory with 0xDEADBEEF. This helps to detect when the program reads memory after its deallocation.

  • The create routine additionally makes a copy of the initialized buffer. The finalizer compares the contents of the buffer and its copy. This way it can detect if an immutable array was altered after its creation.

Range violations might alternatively be detected by range checking techniques. Allocation problems might be solved using Regions. The provided functions might overlook range violations but they help detecting bugs when you have not full control over the code that processes memory content, e.g. when calling external routines via FFI.