-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
assert not working any more in 3.2 #11166
Comments
Any progress ? |
It took me a bit of searching :) Seems that |
cc: @SuGlider |
I'll take a look, but if Matter Library disables it, it can be fixed by Lib Builder for the next release. |
@pschatzmann - I have found a work around that fixes this issue using Core 3.2.0 (or any 3.x). This will undefine |
Thanks a lot for the work around: I confirm that this is working. Looking forward for the final correction... |
@SuGlider what worries me is that matter disables |
Actually, when CHIP builds using release mode, it sets It doesn't affect other IDF components. It doesn't affect esp-matter IDF code or any other IDF component. |
it picks it up because the project files are compiled with this flag. If they are compiled with it, chances are that others are compiled also. We extract flags from the 3 empty files in the lib-builder main (c, cpp and S) |
Board
Any
Device Description
n/a
Hardware Configuration
n/a
Version
latest development Release Candidate (RC-X) and in the meantime also the release 3.2.0
IDE Name
Arduino
Operating System
Linux
Flash frequency
n/a
PSRAM enabled
no
Upload speed
n/a
Description
Up to and including R 3.1 using assert was giving the following type of error messages
assert failed: void setup() file_speeds.ino:100 (SD.begin(PIN_AUDIO_KIT_SD_CARD_CS))
Backtrace: 0x40082541:0x3ffb1f30 0x4008d919:0x3ffb1f50 0x40093afe:0x3ffb1f70 0x400d404b:0x3ffb20a0 0x400dbbbf:0x3ffb2270 0x4008e592:0x3ffb2290
Starting R 3.2 asserts are ignored
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: