Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 404: semicolon not found #404

Merged
merged 1 commit into from
Jan 6, 2017
Merged

Conversation

nurupo
Copy link
Member

@nurupo nurupo commented Jan 6, 2017

Found through cppcheck.


This change is Reviewable

@iphydf iphydf added this to the v0.1.4 milestone Jan 6, 2017
@iphydf
Copy link
Member

iphydf commented Jan 6, 2017

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.


toxcore/crypto_core_mem.c, line 40 at r1 (raw file):

#else
#ifdef _WIN32
    SecureZeroMemory(pnt, len);

len doesn't exist.


Comments from Reviewable

@GrayHatter GrayHatter changed the title Fix missing semicolon Issue 404: semicolon not found Jan 6, 2017
@nurupo
Copy link
Member Author

nurupo commented Jan 6, 2017

toxcore/crypto_core_mem.c, line 40 at r1 (raw file):

Previously, iphydf wrote…

len doesn't exist.

Fixed.


Comments from Reviewable

@nurupo
Copy link
Member Author

nurupo commented Jan 6, 2017

Also fixed the if condition. In libsodium's original code memset_s() is called iff len > 0U, but in ours it was called always.

@GrayHatter
Copy link

:lgtm:


Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


Comments from Reviewable

@iphydf
Copy link
Member

iphydf commented Jan 6, 2017

:lgtm_strong:


Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


Comments from Reviewable

@iphydf iphydf merged commit e7270aa into TokTok:master Jan 6, 2017
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants