50b5f8558e
Xwayland has its own special handling for signals like SIGSEGV/SIGABRT. Instead of leaving the job to the OS, it tries to walk up the call stack (badly, because a lot of information is missing), print the stack trace to stdout, then exit(1). This is very annoying because it prevents Xwayland crashes from being easily debugged. Xwayland has a flag "-core" that aborts instead of exiting. This allows the OS to generate a coredump. It's far from perfect but better than nothing, I guess. |
||
|---|---|---|
| .. | ||
| selection | ||
| meson.build | ||
| server.c | ||
| sockets.c | ||
| sockets.h | ||
| xwayland.c | ||
| xwm.c | ||