diff options
| author | Yingchi Long <i@lyc.dev> | 2024-05-21 01:57:56 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-21 01:57:56 +0800 |
| commit | c6486633d2656faecea8d7eb426bb22c52ddfd14 (patch) | |
| tree | eeff0d213dd8872be261244adaa8d0c78e68d302 /lldb/test/API/python_api/debugger | |
| parent | fd87d765c0455265aea4595a3741a96b4c078fbc (diff) | |
[BPF] report `Invalid usage of the XADD return value"` elegantly (#92742)
Previously `report_fatal_error` is used for reporting something goes
wrong in the backend, but this is confusing because `report_fatal_error`
basically means there are something unexpected & crashed in the backend.
So, turn this "crash" into an elegant error reporting. After this patch,
clang can diagnose it:
bpf-crash.c:4:30: error: Invalid usage of the XADD return value
4 | u32 next_event_id() { return __sync_fetch_and_add(&GLOBAL_EVENT_ID,
1); }
| ^
1 error generated.
Diffstat (limited to 'lldb/test/API/python_api/debugger')
0 files changed, 0 insertions, 0 deletions
