David Malcolm
David Malcolm
This report is incorrect: ../../archer/gdb/python/python.c: In function ‘gdbpy_parameter’: ../../archer/gdb/python/python.c:358:12: error: dereferencing uninitialized pointer: cmd.93->var at ../../archer/gdb/python/python.c:358 [-Werror] I believe this happens because 'cmd' is initialized in a TRY_CATCH in gdb....
I limited the memory available to gcc to 1G, using ulimit. This causes the checker to die with a MemoryError when building gdb. I think this is too much memory;...
When compiling gdb with gcc-with-cpychecker, I see: ../../src/gdb/python/python.c: In function ‘_initialize_python’: ../../src/gdb/python/python.c:1137:1: note: this function is too complicated for the reference-count checker to fully analyze: not all paths were analyzed...
When compiling gdb with gcc-with-cpychecker, I see some errors like this: ../../src/gdb/tui/tui-stack.c:421:32: warning: passing uninitialized data as argument 4 to function: gcc.VarDecl('a') at ../../src/gdb/tui/tui-stack.c:421 [enabled by default] I don't think...
In GCC, a "*" at the beginning of a pass name means that the pass manager should not create a dump file for that pass. I think it might be...
For my project it would be handy to have access to DECL_ASSEMBLER_NAME. This is available on most (but not all) decl nodes, see tree.h.
Currently the plugin generates an HTML file for each function that has some report. However, there is no really easy way to browse all the reports. It would be nice...
I meant `` to cover a sequence of events, but I see now that it could be thought of as representing a stack trace. I think I want a separate...
Many of the badges come in chains. For example, currently I have the "50 successful Koji builds" badge: https://badges.fedoraproject.org/badge/if-you-build-it...-koji-success-iii and was wondering how close I am to the next award...