xianglyc opened a new pull request, #18022: URL: https://github.com/apache/nuttx/pull/18022
*Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary *Update this section with information on why change is necessary, what it exactly does and how, if new feature shows up, provide references (dependencies, similar problems and solutions), etc.* When an interrupt occurs, the hardware automatically pushes the current RIP/RSP onto the interrupt stack. During the interrupt return, the iretq instruction pops them back. The problem is that the RIP/RSP modified by the signal is stored in the XCP context, whereas iretq operates on the interrupt stack. As a result, the RIP/RSP modified by the signal does not take effect in the iretq instruction, causing the task receiving the signal to fail to jump correctly to the signal handler. This behavior appears as if the signal is lost ## Impact no *Update this section, where applicable, on how change affects users, build process, hardware, documentation, security, compatibility, etc.* ## Testing ostest *This section should provide a detailed description of what you did to verify your changes work and do not break existing code.* *Please provide information about your host machine, the board(s) you tested your changes on, and how you tested. Logs should be included.* *For example, when changing something in the core OS functions, you may want to run the OSTest application to verify that there are no regressions. Changes to ADC code may warrant running the `adc` example. Adding a new uORB driver may require that you run `uorb_listener` to verify correct operation.* *Pure documentation changes can just be tested with `make html` (see docs) and verification of the correct format in your browser.* **_PRs without testing information will not be accepted. We will request test logs._** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
