Log syscall name

[JeremyRand]

sockstrace/main.go

Line 546 in 5b2bf7f

logger.Warn().Msgf("Proxy Leak detected, but allowed: %s", address.String())

I think it would be useful to log the syscall name (e.g. connect) that triggered the leak. This would potentially make it a bit easier to understand a core dump and/or stack trace.

[robertmin1]

We already log the currently intercepted syscall prior to any handling, so a log entry for the connect syscall should have been emitted earlier. However, I can include it here as well for added clarity

[JeremyRand]

My concern is that multiple log messages might be interleaved between threads, so putting the syscall name into the same log message that warns about the leak will avoid ambiguity when tracing multithreaded tracees. Also, the current log message containing the syscall name has a lower severity than the leak warning, so it is likely to be suppressed on some setups.