-
Notifications
You must be signed in to change notification settings - Fork 267
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
Set socket to MAX_SOCK_NUM if connection fails #208
Open
goccert25
wants to merge
1
commit into
arduino-libraries:master
Choose a base branch
from
goccert25:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
goccert25
changed the title
Set socket to invalid socket if connection fails
Set socket to MAX_SOCK_NUM if connection fails
Nov 8, 2022
@karlsoderby @per1234 , this is my first time contributing to the Arduino ecosystem. Please let me know if there's anything missing from the PR or anything else you'd like to see from me :) |
Memory usage change @ ec1ed04
Click for full report table
Click for full report CSV
|
Hey @karlsoderby @per1234, bumping this. Is there anyway to move this PR forward? |
per1234
added
topic: code
Related to content of the project itself
type: imperfection
Perceived defect in any part of project
labels
Dec 17, 2022
There is an alternative proposal at #176 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
topic: code
Related to content of the project itself
type: imperfection
Perceived defect in any part of project
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.
I've been experiencing a bug using the Arduino to communicate over ethernet when using multiple EthernetClients, and as far as I can tell this line is the culprit. The exact steps of how the bug happens:
A.connect(HOST, PORT1);
is called first. Inside theconnect
function, the functionsocketBegin
is called, which according to the code here finds the first unused socket number and returns it. Lets say in this case the first unused socket number is 0. This means thatA._socketIndex
ends up being 0.A.connect(HOST, PORT1);
fails on line 63. However, note thatA._socketIndex
is NOT reset back toMAX_SOCK_NUM
and stays at the initialized value (for this example we'll stick with 0).B.connect(HOST, PORT2);
is called second. The process as above happens, andB._socketIndex
is set to 0. However, for some reasonB.connect(HOST, PORT2);
works, and B is able to connect.B._socketIndex == A._socketIndex == 0
. However, sinceA.connect(HOST, PORT1)
returned 0 (which stands for false), calls toA.available()
,A.read()
shouldn't work. Instead, they do work, and even worseA.write()
will write data to the socket that B is connected to.This change should fix the bug, because instead of returning 0 on line 63 we break, we set
_socketIndex
back toMAX_SOCK_NUM
and everything behaves as expected.