Hoed: Lightweight algorithmic debugging.

[ bsd3, debug, library, trace ] [ Propose Tags ] [ Report a vulnerability ]

Hoed is a tracer and debugger for the programming language Haskell.

To locate a defect with Hoed you annotate suspected functions and compile as usual. Then you run your program, information about the annotated functions is collected. Finally you connect to a debugging session using a webbrowser.

Hoed comes in two flavours: Hoed.Pure and Hoed.Stk. Hoed.Stk uses the cost-centre stacks of the GHC profiling environment to construct the information needed for debugging. Hoed.Pure is recommended over Hoed.Stk: to debug your program with Hoed.Pure you can optimize your program and do not need to enable profiling.


[Skip to Readme]

Flags

Automatic Flags
NameDescriptionDefault
buildexamples

Build example executables.

Disabled
validatepure

Build test cases to validate Hoed-pure.

Disabled
validatestk

Build test cases to validate Hoed-stk.

Disabled
validategeneric

Build test cases to validate deriving Observable for Generic types.

Disabled
validateprop

Build test cases to validate deriving judgements with properties.

Disabled

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

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.1.0.0, 0.1.0.1, 0.2.0, 0.2.1, 0.2.2, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.4.0, 0.4.1, 0.5.0, 0.5.1
Change log changelog
Dependencies array, base (>=4 && <5), containers, deepseq, directory, extensible-exceptions, filepath, FPretty, Hoed, lazysmallcheck, libgraph (==1.9), mtl, network, process, QuickCheck, random, RBTree (==0.0.5), regex-posix, template-haskell, threepenny-gui (>=0.6 && <0.7), unix, utf8-string, X11 (>=1.5 && <1.7) [details]
License BSD-3-Clause
Copyright (c) 2000 Andy Gill, (c) 2010 University of Kansas, (c) 2013-2015 Maarten Faddegon
Author Maarten Faddegon
Maintainer hoed@maartenfaddegon.nl
Category Debug, Trace
Home page http://maartenfaddegon.nl
Source repo head: git clone git://github.com/MaartenFaddegon/Hoed.git
Uploaded by faddegon at 2015-12-14T13:13:01Z
Distributions
Reverse Dependencies 4 direct, 0 indirect [details]
Executables hoed-tests-Stk-IndirectRecursion, hoed-tests-Stk-Example4, hoed-tests-Stk-Example3, hoed-tests-Stk-Example1, hoed-tests-Stk-Insort2, hoed-tests-Stk-DoublingServer, hoed-tests-Pure-t7, hoed-tests-Pure-t6, hoed-tests-Pure-t5, hoed-tests-Pure-t4, hoed-tests-Pure-t3, hoed-tests-Pure-t2, hoed-tests-Pure-t1, hoed-tests-Generic-t3, hoed-tests-Generic-r3, hoed-tests-Generic-t2, hoed-tests-Generic-r2, hoed-tests-Generic-t1, hoed-tests-Generic-r1, hoed-tests-Generic-t0, hoed-tests-Generic-r0, hoed-tests-Prop-t4, hoed-tests-Prop-t3, hoed-tests-Prop-t2, hoed-tests-Prop-t1, hoed-tests-Prop-t0, hoed-examples-Expression_simplifier__with_properties, hoed-examples-Expression_simplifier, hoed-examples-Parity_test, hoed-examples-Simple_higher-order_function, hoed-examples-Digraph_not_data_invariant__with_properties, hoed-examples-CNF_unsound_de_Morgan__with_properties, hoed-examples-SummerSchool_compiler_does_not_terminate__with_properties, hoed-examples-SummerSchool_compiler_does_not_terminate, hoed-examples-XMonad_changing_focus_duplicates_windows__with_properties, hoed-examples-XMonad_changing_focus_duplicates_windows__CC, hoed-examples-XMonad_changing_focus_duplicates_windows, hoed-examples-Insertion_Sort_elements_disappear, hoed-examples-Nub-defective-sort__with_properties, hoed-examples-Salary, hoed-examples-Rot13, hoed-examples-FPretty_indents_too_much__CC, hoed-examples-FPretty_indents_too_much
Downloads 12515 total (37 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2015-12-14 [all 1 reports]

Readme for Hoed-0.3.3

[back to package description]

Hoed - A Lightweight Haskell Tracer and Debugger Build Status

Hoed is a tracer and debugger for the programming language Haskell. To locate a defect with Hoed you annotate suspected functions and compile as usual. Then you run your program, information about the annotated functions is collected. Finally you connect to a debugging session using a webbrowser. See the

Project homepage

for more information on what it does and how you can use it to find bugs in your code.