a46de84f89
When a page fault cannot be resolved, the GDB monitor can get a hint about which thread faulted by evaluating the thread state object returned by 'Cpu_session::state()'. Unfortunately, with the current implementation, the signal which informs GDB monitor about the page fault is sent before the thread state object of the faulted thread has been updated, so it can happen that the faulted thread cannot be determined immediately after receiving the signal. With this commit, the thread state gets updated before the signal is sent. At least on base-nova it can also happen that the thread state is not accessible yet after receiving the page fault notification. For this reason, GDB monitor needs to retry its query until the state is accessible. Fixes #1206. |
||
|---|---|---|
| .. | ||
| 32bit/base | ||
| 64bit/base | ||
| arm | ||
| base | ||
| cap_session | ||
| cpu | ||
| cpu_session | ||
| dataspace | ||
| drivers | ||
| io_mem_session | ||
| io_port_session | ||
| irq_session | ||
| log_session | ||
| pager | ||
| parent | ||
| pd_session | ||
| platform | ||
| ram_session | ||
| rm_session | ||
| rom_session | ||
| root | ||
| session | ||
| signal_session | ||
| thread | ||
| trace_session | ||
| util | ||
| x86/cpu | ||
| x86_32/cpu | ||
| x86_64/cpu | ||
| README | ||
This directory contains include files of interfaces that are exported by components to be used by other components. Each subdirectory corresponds to the component exporting the interface.