You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The change also affects the /proc/{pid}/task/{pid}/comm file.
Shouldn't using getters not modify the results in any way?
I'm on Linux (RHEL8) using setproctitle 1.3.3. I also could reproduce this in a debian container (docker.io/library/python:3.12)
Not sure if related, but with debug logging on I also see a message about "setup was called more than once!":
$ SPT_DEBUG=1 python issueexample.py
[SPT]: module init
[SPT]: reading argc/argv from Python main
[SPT]: found 2 arguments
[SPT]: walking from environ to look for the arguments
[SPT]: found environ at 0x7fffffffb5d4
[SPT]: found argv[1] at 0x7fffffffb5c4: issueexample.py
[SPT]: argv[0] should be at 0x7fffffffb5bd
[SPT]: found argv[0]: python
[SPT]: environ has been copied
0. python python issueexample.py
[SPT]: setup was called more than once!
1. python issueexa python issueexample.py
The text was updated successfully, but these errors were encountered:
I found something that seems undesirable - when using
getproctitle()
the result returned bygetthreadtitle()
seems to mutate.Minimal reproducer:
Demo:
The change also affects the
/proc/{pid}/task/{pid}/comm
file.Shouldn't using getters not modify the results in any way?
I'm on Linux (RHEL8) using setproctitle 1.3.3. I also could reproduce this in a debian container (docker.io/library/python:3.12)
Not sure if related, but with debug logging on I also see a message about "setup was called more than once!":
The text was updated successfully, but these errors were encountered: