From 5bd36fdff16871eb7d06fc26cac07e7f2703432b Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Thu, 29 Nov 2012 01:33:22 +0100
Subject: IRC.

---
 open_issues/code_analysis/discussion.mdwn | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

(limited to 'open_issues/code_analysis')

diff --git a/open_issues/code_analysis/discussion.mdwn b/open_issues/code_analysis/discussion.mdwn
index f8a0657d..6f2acc08 100644
--- a/open_issues/code_analysis/discussion.mdwn
+++ b/open_issues/code_analysis/discussion.mdwn
@@ -42,3 +42,20 @@ License|/fdl]]."]]"""]]
       tool, please add it to open_issues/code_analysis.mdwn
     <antrik> (I guess we should have a "proper" page listing useful debugging
       tools...)
+
+
+## IRC, freenode, #hurd, 2012-09-03
+
+    <mcsim> hello. Has anyone tried some memory debugging tools like duma or
+      dmalloc with hurd?
+    <braunr> mcsim: yes, but i couldn't
+    <braunr> i tried duma, and it crashes, probably because of cthreads :)
+
+
+## IRC, freenode, #hurd, 2012-09-08
+
+    <mcsim> hello. What static analyzer would you suggest (probably you have
+      tried it for hurd already)?
+    <braunr> mcsim: if you find some good free static analyzer, let me know :)
+    <pinotree> a simple one is cppcheck
+    <mcsim> braunr: I'm choosing now between splint and adlint
-- 
cgit v1.2.3