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

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

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 0.0, 0.0.1, 0.0.1
Change log None available
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:44:42Z


[Index] [Quick Jump]


Manual Flags


Add stress tests and integrity checks to allocations


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


Maintainer's Corner

Package maintainers

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:

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.