On 2012/10/28 15:48:45, r wrote:
The file names are inappropriate now.
The file names are inappropriate now.
a bit too long, and exec might confuse with the exec syscall.
how about the original execpath?
For Plan 9, it depends what you want this for. /proc/PID/text is
always a working name for the executable. Otherwise I don't know if
it's possible.
I've thought about /proc/PID/text, in fact it can pass the test, butalways a working name for the executable. Otherwise I don't know if
it's possible.
i think the main use of this to determine the original binary's path
so that the binary can access its bundled asset files, for example.
i'd also like to test we can indeed find the other files around the
binary, but given the current go test's behavior, this is difficult
to test.
https://codereview.appspot.com/6736069/
