aboutsummaryrefslogtreecommitdiff
path: root/open_issues/code_analysis
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2012-12-30 00:36:20 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2012-12-30 00:36:20 +0100
commite9235e964397bc2c5c6ca1858aba5c098b591660 (patch)
treef105012a160e801e96ec81f2d26b447deb835d08 /open_issues/code_analysis
parentd90af7499de9d0c58215691174826f956ff6612c (diff)
parent55ffc6f5698b61c75260ff12b2591e3032b0651e (diff)
downloadweb-e9235e964397bc2c5c6ca1858aba5c098b591660.tar.gz
web-e9235e964397bc2c5c6ca1858aba5c098b591660.tar.bz2
web-e9235e964397bc2c5c6ca1858aba5c098b591660.zip
Merge branch 'master' of git.savannah.gnu.org:/srv/git/hurd/web
Diffstat (limited to 'open_issues/code_analysis')
-rw-r--r--open_issues/code_analysis/discussion.mdwn29
1 files changed, 18 insertions, 11 deletions
diff --git a/open_issues/code_analysis/discussion.mdwn b/open_issues/code_analysis/discussion.mdwn
index f8a0657d..7ac3beb1 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,7 +27,25 @@ 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
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