rofl0r

> okay. this is an executable file. doesn't open in any editor. > so which process is starting it (it's the process that owned or created that pid, just find...

> I did that you did what ? if you move the real 32bit steam binary i mentioned in https://github.com/rofl0r/proxychains-ng/issues/386#issuecomment-884955833 to another location and replace it with a shell script...

> So a WONTFIX ? OP closed the issue himself. there's nothing proxychains-ng can do to fix the situation, apart from having some kind of "how-to" for this specific scenarion....

> This does not work because steam restores all its startup scripts and executables when it launches. from where ?

that's a pity. so it looks the only option left is to ask steam upstream to either - provide built-in support for proxy use - compile **all** binaries as 32...

can you run the same command via gdb so we can get a backtrace? thanks

it seems libc malloc detected a double-free or a similar condition and called abort() so the program stops executing rather than causing exploitable memory corruption. why that happens i can't...

i personally don't see much value in such an addition; i'd probably just use different config files for different programs/endpoints. but if you have usecases where it makes sense and...

for the record, tinyproxy has some features that could enable use cases as described above. for example, the use case described by @Nothing4You you'd run a tinyproxy on localhost that...

could you provide a backtrace of the crash ? `gdb --args proxychains4 nmap ....options...` then type r and wait for the crash, then type bt and paste the output.