![]() Using an eBPF/ bcc tool to look for exit reasons: I may need to increase the core file size ulimits for Slack, but that might mean mucking around with its startup scripts I'll try some other tracing first. This didn't work: No core file showed up. # echo "/var/cores/core.%e.%p.%h.%t" > /proc/sys/kernel/core_pattern Redirecting them to the file system so I can then do core dump analysis using gdb(1), as root: I'm guessing it's core dumping and Ubuntu's apport is eating them. Note that I don't know anything about Slack internals, and there may be better ways to solve this. I'm experimenting with this "rough notes" format as a way to quickly share things. I spend many hours documenting advanced debugging stories for books, talks, and blog posts, but many things I never have time to share. These are rough notes for how I debugged it, in case it's useful for someone searching on this topic. A quick internet search revealed nothing. It usually happened when locking and unlocking the screen. ![]() ![]() I'd Alt-Tab and find it was no longer there. I run the Slack messaging application on Ubuntu Linux, and it recently started mysteriously crashing. Systems Performance: Enterprise and the Cloud, 2nd Edition How To Add eBPF Observability To Your ProductīPF binaries: BTF, CO-RE, and the future of BPF perf tools USENIX LISA2021 Computing Performance: On the Horizon USENIX SREcon APAC 2022: Computing Performance: What's on the Horizon
0 Comments
Leave a Reply. |