Hi!
Thank you for the answer, Mark!
Does the tor process shut down before the crash reporter can
do its thing?
No, it doesn't (it waits for crash reporter), I also checked Google breakpad, it uses libcurl, so it supports SOCKS, I hardcoded our IP and port, but still haven't built it.
Sorry for delay, I busy with internship interview stuff :/
Kind regards, Nur-Magomed (nmago)
2017-11-11 20:31 GMT+03:00 Tom Ritter tom@ritter.vg:
On 9 November 2017 at 08:35, Mark Smith mcs@pearlcrescent.com wrote:
I am not sure what the best solution is, but I assume the idea is to use the already running tor deamon to submit crash reports. Will the tor daemon still be running after the browser process crashes (Tor Launcher uses the TAKEOWNERSHIP control port command to arrange for tor to shutdown when the firefox process does).
That is a good question. We had this working before, but then we discovered this new need-the-proxy-settings problem. nmago, what have you seen? Does the tor process shut down before the crash reporter can do its thing?
One way you can test this is to hardcode the crash reporter to get the proxy settings from an environment variable, launch tor browser, figure out the listening port using netstat, and then set the environment variable to the correct port.
-tom