diff options
Diffstat (limited to 'open_issues/code_analysis/discussion.mdwn')
| -rw-r--r-- | open_issues/code_analysis/discussion.mdwn | 29 |
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 |