3 ms·
Doesn't even need to go this hardcore; simply reading the verbose output would show where things are getting stuck.
by ThePowerOfFuet 7y ago
Doesn't even need to go this hardcore; simply reading the verbose output would show where things are getting stuck.
- 0x0 7y agoThe verbose output didn't seem to point out the exact system call or libc call that got stuck. A lldb/gdb bt stacktrace could pinpoint what's hanging (for example, some people mentioned parsing /etc/services). I don't think this has been resolved yet?