db5e43967c
## Problem The `valgrind?check=new` API parameter uses `VALGRIND_DO_NEW_LEAK_CHECK` which is only available in Valgrind 3.21+. On older versions like CentOS's default Valgrind 3.16, this causes undefined behavior since the macro is not defined. ## Solution - Check for `VALGRIND_DO_NEW_LEAK_CHECK` availability before processing the request - Return `ERROR_NOT_SUPPORTED` with version information when unsupported - Move the version check before thread creation to avoid unnecessary resource allocation ## Changes - Early validation of `check=new` parameter compatibility - Proper error response with current Valgrind version details - Prevents undefined behavior on older Valgrind installations Fixes compatibility issues with older Valgrind versions commonly found in enterprise Linux distributions. --------- Co-authored-by: Jacob Su <suzp1984@gmail.com> Co-authored-by: winlin <winlinvip@gmail.com> Co-authored-by: OSSRS-AI <winlinam@gmail.com> |
||
|---|---|---|
| .. | ||
| Architecture.md | ||
| CHANGELOG.md | ||
| Dockers.md | ||
| Features.md | ||
| ffmpeg-logo.png | ||
| ffmpeg-min.png | ||
| PERFORMANCE.md | ||
| README.md | ||
| readme.txt | ||
| Resources.md | ||
| source.200kbps.768x320.flv | ||
| source.flv | ||
| srs-logo.ico | ||
| srs-logo.png | ||
