Debugger: Move debug output accessing after check whether err != Null #511
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b4n
reviewed
Dec 18, 2016
| if (err) | ||
| { | ||
| #ifdef DEBUG_OUTPUT |
There was a problem hiding this comment.
style: the preproc directives used not to be indented
There was a problem hiding this comment.
Actually I was thinking about whether or not but decided for personal reasons ;)
|
I just having Geany configured to purge trailing spaces etc so in the end its all cleaner. |
frlan
deleted the
fix/debugger/prevent_from_possible_nullpointer_dereference
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The debug-output is accessing err. If err is Null, it will fail most likely.