Yes, this will be the case on master. On 3.3.x I chose to hide the error because this function is mostly called with ARGV0 as procname, and I set ARGV0 manually in a bunch of different places. I might have missed one or two binaries, but we don't have time to catch this.