envp PWD=

[apitrace]

envp PWD=

[zackr]

I'm sorry, I don't understand. What is this about?

[dacresni]

there is a line in the master branch of your os_posix.cpp file of apitrace and I was giving you a posix portable way to get the absolute path of the executable sense there's a comment requesting it on line 64. You just have to concatenate the PWD environmental variable with argv[0] of your argument vector to get the absolute path. (Instead of trying to read the proc file system) I was going to provide example code but i didn't want to forget. // http://stackoverflow.com/questions/1023306/finding-current-executables-path-without-proc-self-exe.

[zackr]

Ah, no, that's not what it is. The code in question is also in a library, which doesn't have the access the argv vector so we can't rely on it.

[dacresni]

but getenv should work, shouldn't it?

On Thu, Apr 28, 2011 at 10:40 PM, zackr <
[email protected]>wrote:

Ah, no, that's not what it is. The code in question is also in a library,
which doesn't have the access the argv vector so we can't rely on it.

Reply to this email directly or view it on GitHub:
#11 (comment)

"lalalalala! it's not broken because I can use it"

http://linux.slashdot.org/comments.pl?sid=194281&threshold=1&commentsort=0&mode=thread&cid=15927703

[zackr]

No, there's no env variable for the currently running process name.

[dacresni]

have you tried it? That behavior seems contrary to posix. http://publib.boulder.ibm.com/infocenter/zos/v1r10/index.jsp?topic=/com.ibm.zos.r10.bpxbd00/getenv.htm
I just think it would be strange if it didn't work. This isn't just a GNU libC thing, its a posix thing.

[zackr]

Tried what? What behavior? That environment doesn't have a variable holding currently running process name? It never did.