-
Notifications
You must be signed in to change notification settings - Fork 22
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
SoftwareSerial bug - local variable, dangling pointer #19
Comments
I think you're, right. If I remember correctly, I tested this feature with actual HW when I implemented this feature, but I probably hit an undefined behavior of the uC tool-chain. Will you be interested on submitting a patch/PR? |
Yes! I have an idea to declare "Serial" outside and pass it to pointer initialization (it will be completely analogous to "HardwareSerial"). And make the incoming pointer type "Stream". This will allow you to use any "Serial" and even their non-standard implementations. |
Awesome! |
fixed on #20 |
I look at this code and see an error (explain in cppreference).
The variable
serial
is local (in stack), its lifetime is limited to the area of the constructor. After exiting the constructor, the variableserial
will be destroyed, and the variableuart
will contain dangling pointer. Copying its address should not prolong the lifetime.I tried looking for some special case that affects the lifetime of a variable and which will not be "undefined behavior" (0, 1, 2, 3, 4, 5, 6 ). But I couldn't find anything suitable for this code...
If my fears are in vain, please give me a link to a description of this case in the standard or explain how it works.
Problem code:
The text was updated successfully, but these errors were encountered: