effective-debugging
effective-debugging copied to clipboard
Code examples used in the book Effective Debugging (Addison-Wesley, 2016)
When programming in Python, import the `pprint` module and use its `PrettyPrinter` **method**. should be read as When programming in Python, import the `pprint` module and use its `PrettyPrinter` **class**....
`angle = angle - 2 * Math.PI * Math.floor(angle / (2 * Math.PI)));` should be read as `angle = angle - 2 * Math.PI * Math.floor(angle / (2 * Math.PI));`...
`as a nifty graphical debugger or dtrace (see Item 58: “Trace the Code’s` should be read as `as a nifty graphical debugger or DTrace (see Item 58: “Trace the Code’s`...
in the `windows/system32` directory. Should be read as in the `Windows/system32` directory. Thanks to: Toshiaki Kurokawa
The second command for deleting for aborting the failed experiment ``` $ git checkout -D issue-work-1234 ``` should be read as ``` $ git branch -D issue-work-1234 ``` Spotted and...
The command for invoking *findbugs* ``` $ java -jar findbugs.jar -textui Counter.class ``` should be read as ``` $ findbugs -textui Counter.class ``` Spotted and corrected by Naohiro Ooiwa-san.
The line ``` if ! [ -f ~/.bash_completion.d/git-completion.bash] ; then ``` should read ``` if ! [ -f ~/.bash_completion.d/git-completion.bash ] ; then ``` Thanks to: Naohiro Ooiwa-san
The listing should be read as follows, correcting the order of the defined breakpoints. ``` # Define a counter variable to keep track of locks set $nlock = 0 #...
"such as cURL to fetch URLs and jq to parse JSON data," should be read as "such as curl to fetch URLs and jq to parse JSON data," Thanks to:...
Page 30, Item 12, line 7-8 from top ```C #include "lua5.2/lua.h" #include "lua5.2/lauxlib.h" ``` Should be read as ```C #include #include #include ``` Thanks to Oiwa-san.