-
Notifications
You must be signed in to change notification settings - Fork 217
ATT_OP_FIND_INFO_RESP incorrect processing during ATTClass::discoverDescriptors causes crashing #245
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
type: imperfection
Perceived defect in any part of project
Comments
carterd
added a commit
to carterd/ArduinoBLE
that referenced
this issue
Sep 25, 2022
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to stm32duino/STM32duinoBLE
that referenced
this issue
Mar 21, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to stm32duino/STM32duinoBLE
that referenced
this issue
Mar 21, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to stm32duino/STM32duinoBLE
that referenced
this issue
Mar 27, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to stm32duino/STM32duinoBLE
that referenced
this issue
Mar 28, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to fpistm/STM32duinoBLE
that referenced
this issue
Apr 17, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
fpistm
pushed a commit
to fpistm/STM32duinoBLE
that referenced
this issue
Apr 17, 2025
… processing during ATTClass::discoverDescriptors causes crashing I've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Uh oh!
There was an error while loading. Please reload this page.
Symptoms:
Connecting as Central to 'other' BLE device which responds with
ATT_OP_FIND_INFO_RESP
using 128-bit UUIDs causes crash!Location of Issue:
FILE =
ArduinoBLE\src\utility\ATT.cpp
FUNC =
bool ATTClass::discoverDescriptors(uint16_t connectionHandle, BLERemoteDevice* device)
LINE = 1728-1730 (ish)
Explanation:
responseBuf[1]
ofATT_OP_FIND_INFO_RESP
is the format of the response as follows:0x01 = 2 octets of handle, 2 octets of UUID [total 4 octets/bytes]
0x02 = 2 octets of handle, 16 octets of UUID [total 18 octets/bytes]
Current:
Possible Fix:
THANKS GUYS!!!!
The text was updated successfully, but these errors were encountered: