4 ms·
It was actually my coworker Joshua who first noticed that, and then that dredged up a long-forgotten memory in me of having seen stacker on crates.io. Many eyes
by sunshowers 2y ago
It was actually my coworker Joshua who first noticed that, and then that dredged up a long-forgotten memory in me of having seen stacker on crates.io. Many eyes make bugs shallow!
Agree about the power of brute force solutions! When you're struggling to get a foothold, those kinds of approaches are extremely helpful. For the cwd thing specifically, it was clear in hindsight, and I should have known about it (having written nextest which has to handle crate cwds carefully). But I don't beat myself up too much over it, and now I know where to look next time this happens.
- inferiorhuman 2y agoIn BSD land you can specify the path and filename pattern for the core dump via a sysctl knob (kern.corefile). quick check of the docs On Solaris or Illumos I'd eye coreadm(8) and maybe chuck something like this in my shell login script: coreadm -p $HOME/coredumps/core.%f.%p That'll put the executable name and PID in the dump filename and leave them all in ~/coredumps/… for all processes that are children of that login shell.
- sunshowers 2y agoTrue, that would have worked as well. Plenty of ways to do it.