Skip to content

Fixed issue #25. Possible corruption in attachInterrupt. #34

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

Closed
wants to merge 1 commit into from
Closed

Fixed issue #25. Possible corruption in attachInterrupt. #34

wants to merge 1 commit into from

Conversation

NormanDunbar
Copy link

Pull Request created as requested for Issue #25:

digitalPinToInterrupt() may return NOT_AN_INTERRUPT if an invalid pin given.
attachInterrupt() and detachInterrupt() both need to check for this value or they risk
corrupting memory just before intFunc[]. Effectively corrupting intFunc[-1].

digitalPinToInterrupt may return NOT_AN_INTERRUPT if an invalid pin given.
attachInterrupt and detachInterrupt need to check for this or they risk
corrupting memory just before intFunc[].

Please enter the commit message for your changes. Lines starting
@facchinm facchinm added this to the next milestone Oct 29, 2018
@aweatherguy
Copy link

aweatherguy commented Nov 15, 2018

I noticed an issue with this pull request...maybe no fix is necessary. See my comments in the originating issue:

#25

@NormanDunbar
Copy link
Author

I think, due to the ongoing discussions in #25 that I'm going to discontinue this pull request as it is not quite correct. Yet.

There's still more work to be done here on the basis of signed and unsigned 8 bit ints being passed around between digitalPinToInterrupt() and attachInterrupt().

I'll be back! :-)

Cheers,
Norm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants