1 files changed, 44 insertions, 0 deletions
diff --git a/open_issues/code_analysis/discussion.mdwn b/open_issues/code_analysis/discussion.mdwn
new file mode 100644
index 00000000..f8a0657d
--- /dev/null
+++ b/open_issues/code_analysis/discussion.mdwn
@@ -0,0 +1,44 @@
+[[!meta copyright="Copyright © 2011, 2012 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_documentation]]
+
+[[!toc]]
+
+
+# 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?
+    <braunr> you will have to adapt it
+    <braunr> but it's already designed to handle custom allocators
+    <braunr> iirc
+    <braunr> btw, are there special flags for that memory which the pager
+      allocates ?
+    <braunr> e.g. to use wired memory ?
+    <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
+      tools...)