diff options
| author | Jon Turney <jon.turney@dronecode.org.uk> | 2024-01-12 00:34:27 +0300 |
|---|---|---|
| committer | Jon Turney <jon.turney@dronecode.org.uk> | 2024-01-16 17:07:07 +0300 |
| commit | aa8224826cb4d7d436757688e8cb3fb760f1aabc (patch) | |
| tree | d5f5e55430270334b33f6b3cfac489ea06f1d7f3 /winsup/doc | |
| parent | a83b93e662b0e65fd181ed50de7e960b311f4a94 (diff) | |
Cygwin: Treat api_fatal() similarly to a core-dumping signal
Provide the same debugging opportunities for api_fatal() as we do for a
core-dumping signal:
1) Break into any attached debugger
2) Start JIT debugger (if configured) (keeping these under DEBUGGING doesn't seem helpful)
3) Write a coredump (if rlim_core > 1MB)
4) Write a stackdump (if that failed, or 0 < rlim_core <= 1MB)
Diffstat (limited to 'winsup/doc')
0 files changed, 0 insertions, 0 deletions