14fb39a6cd
The elf_emit() function in coredump.c was only checking for negative returnvalues from lib_stream_puts() to detect write failures. However, lib_stream_puts()can return 0 to indicate that no bytes were written (e.g., due to stream full,end-of-file, or other non-error conditions that prevent data writing). This oversight meant that cases where lib_stream_puts() returned 0 would bypassthe error handling, leading to incomplete data emission in the core dump withoutany failure indication. The loop would continue attempting to write the remainingdata, resulting in partial or corrupted core dump files. This fix modifies the condition from ret < 0 to ret <= 0 to: 1. Catch both error conditions (negative return values) and zero-byte writes. 2. Immediately break the write loop and propagate the failure, ensuring the core dump process correctly aborts when data cannot be written. This change improves the reliability of core dump generation by ensuring allfailed or incomplete write attempts are properly handled, preventing corruptedcore dump files. Signed-off-by: chao an <anchao.archer@bytedance.com> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.