Hacker News new | past | comments | ask | show | jobs | submit login

You can do the exact same with a few lines of bash and the gdb package which includes gcore, a standard utility that saves core files from running programs.



I guess the sampling and triggering part is the idea.

There's an "explain vs gcore" issue on the github, which mentions among other things that they use gcore to generate the core dumps but want to move away from it: https://github.com/Microsoft/ProcDump-for-Linux/issues/13


So this is kind of more like perf, which includes sampling and triggering both?


I don't know, pointers to relevant perf functionality would be welcome. I just looked and couldn't find an obvious way to get core dumps frpm memory or cpu usage thresholds.


Doing things simple and fast is not the Microsoft way. The goal is to abstract everything from the user to that they become helpless and dependent on bloated interfaces.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: