Mingjie Shen
Mingjie Shen
### Operating System Linux ### Board N/A ### Firmware examples/device/uac2_headset/src/main.c ### What happened ? https://github.com/hathach/tinyusb/blob/2720392a154dac5ff4529fbcc16c0a0718c9c8af/examples/device/uac2_headset/src/main.c#L234 The condition `UAC2_ENTITY_SPK_FEATURE_UNIT` looks unusual (it is always true). Is this intentional? ### How to...
The local variable result is never initialized if i_bytes >= i_end.
https://github.com/contiki-ng/contiki-ng/blob/38957608f30964e1f0268ff0e844ca196268650d/os/services/lwm2m/lwm2m-engine.c#L1599-L1602 `bnum` and `bsize` are uninitialized in line 1602 if the condition `(offset != NULL && *offset == 0)` does not hold: https://github.com/contiki-ng/contiki-ng/blob/38957608f30964e1f0268ff0e844ca196268650d/os/services/lwm2m/lwm2m-engine.c#L1559-L1562
https://github.com/gozfree/gear-lib/blob/bffbfd25af4ff7b04ebfafdab391b55270b0273e/gear-lib/librtsp/rtp.c#L383 The variable `ret` may not be initialized at this access.
https://github.com/gozfree/gear-lib/blob/bffbfd25af4ff7b04ebfafdab391b55270b0273e/gear-lib/librtmpc/hashswf.c#L272 This 'call to strcpy' may overflow the destination.
PRI macros should be used for uintptr_t. Calling a printf-like function with the wrong type of arguments causes unpredictable behavior.
As stated in [README.md](https://github.com/raspberrypi/pico-sdk/tree/master/src/rp2_common#readme), hardware_* are Hardware Abstraction Layer (HAL), while pico_* provide higher level functionality. I have noticed that some code in pico_* accesses memory-mapped I/O (MMIO) without going...