Re: [Openocd-development] clang static analyzer

2011-10-18 Thread Marti Bolivar
/delurk I ran scan-build from today's llvm and clang trunks on openocd commit 0dac042a107f000936995ea468c3fa02b9896fb6 as follows: $ scan-build ./configure --enable-maintainer-mode $ scan-build make The result was a directory full of HTML reports. They're readable in firefox, but the output

Re: [Openocd-development] clang static analyzer

2011-10-19 Thread Marti Bolivar
On 10/19/2011 03:51 AM, Jon Povey wrote: openocd-development-boun...@lists.berlios.de wrote: I'd like to see patches having to pass clang static analyzer unscathed before they're ready for review :-) I had a quick look at that output, interesting. Some looked like real bugs, but others it

Re: [Openocd-development] clang static analyzer

2011-10-21 Thread Marti Bolivar
On 10/21/2011 10:40 AM, Øyvind Harboe wrote: Where does the output go? It should go in a directory named scan-build--MM-DD-n/, where n starts from 1. If I recall correctly, that directory ended up in the directory I ran scan-build from. scan-build ./configure

Re: [Openocd-development] git gui

2011-10-27 Thread Marti Bolivar
On 10/27/2011 06:43 AM, Luca Ottaviano wrote: Having a GUI for hunk selection and commit is by far fastest then jumping trough various shells when writing a meaningful changelog message for the changes you are committing. +1. I use magit from within emacs for this (among other things). The