summaryrefslogtreecommitdiff
path: root/open_issues/code_analysis
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2012-10-23 12:04:41 +0200
committerThomas Schwinge <thomas@codesourcery.com>2012-10-23 12:04:41 +0200
commita61e4bc35f25bc361cde5a973334424c0c1fc5bf (patch)
tree4ea36dddd3241ebd6f0722d0d7fffb51a759cc4b /open_issues/code_analysis
parenta29dec0b89f2961c8af41e6cd851b4ed9c9d28d8 (diff)
open_issues/code_analysis: Splint.
Diffstat (limited to 'open_issues/code_analysis')
-rw-r--r--open_issues/code_analysis/discussion.mdwn12
1 files changed, 1 insertions, 11 deletions
diff --git a/open_issues/code_analysis/discussion.mdwn b/open_issues/code_analysis/discussion.mdwn
index f8a0657d..f6b1e8c1 100644
--- a/open_issues/code_analysis/discussion.mdwn
+++ b/open_issues/code_analysis/discussion.mdwn
@@ -15,17 +15,6 @@ License|/fdl]]."]]"""]]
# IRC, freenode, #hurd, 2011-12-04
- <mcsim> has anyone used splice on hurd?
- <mcsim> splice -> splint
- <youpi> not that I know of
- <mcsim> this is tool for statically checking C programs
- <mcsim> seems I made it work
- <braunr> hm i realli i personnally dislike such tools a lot, but sometimes
- it might help
- <braunr> hello hurd people
- <mcsim> braunr: hello
- <braunr> mcsim: duma may be helpful as replacement for the memcheck part of
- valgrind
<mcsim> defpager uses it's own dynamic memory allocator, which uses
vm_allocate/vm_deallocate as backing store? Am I able to use duma in such
case?
@@ -38,6 +27,7 @@ License|/fdl]]."]]"""]]
<mcsim> yes, wired memory
<braunr> you'll have to change that in duma then
<braunr> but apart from such details, it should be straightforward
+
<antrik> braunr: I have no idea about duma; but if you think it's a useful
tool, please add it to open_issues/code_analysis.mdwn
<antrik> (I guess we should have a "proper" page listing useful debugging