The code is resistant to a simple binary chop: I suspect due to the points in the problem path being in more than one area of the file. I can lose 1000 lines near the top, but that is about it. It does depend on a couple of include files, I think to get the class / function definitions. I bit the bullet and compiled from source so can tell from the backtrace in gdb that it is bouncing between lines 110 and 123 of pathanalysis.cpp. I even added some debug output to forwardRange to try and find the...
We recently upgraded from cppcheck 2.4.1 to 2.6 and now find that cppcheck gets stuck processing a specific file. The file is ~3.5ksloc and seems to depend on other files (presumably the includes) so is not practical to post as an issue (and is closed source). While checking v2.5 and compiling / running gdb on the latest version is on my TODO list it will take a while to reach the top, so I generated stack traces, using pstack, which suggests it has got stuck in CheckStl::invalidContainer() with...
SSDP not working reliably on Mac OS X Mavericks
I agree it is a duplicate. I didn't notice the previous feature request when I c...
I've asked for path #104 to be closed as the current version compiles on mac - IFF_SLAVE...
This issue has been fixed by another method in the current git repo, so feel free...
Initial import of code.
Create standard directories.