Hi, FYI, a fix for this will be released as part of 0.4.2.6 and 0.4.1.8 (only 0.4.1.7 was affected in the 0.4.1.x series). See https://trac.torproject.org/projects/tor/ticket/32841
Regards Peter Peter Gerber: > Hi, > > This doesn't look like 32841 to me. The crash appears to be caused by a > call to dup() newly added in 0.4.2.x [1]. I'm having trouble reproducing > the issue though. The code appears to handle log output. Do you have any > custom 'Log' configurations in your torrc? > > Regards > > Peter > > > [1]: > https://gitweb.torproject.org/tor.git/commit/?id=a22fbab98690f802ae3bda276078cc7fc767feba > > Roger Dingledine: >> On Sun, Jan 05, 2020 at 08:18:53AM +0100, tor-re...@riseup.net wrote: >>> just a little update: >>> >>> I've reproduced this bug on my laptop with Debian Buster. >>> >>> I've noticed that this problem occurs only with tor 0.4.2.5. Tor 0.4.1.6, >>> from Debian buster backports repository, works properly. >> >> Hi! Yes, this is ticket >> https://bugs.torproject.org/32841 >> >> I am hoping that when folks get back from their holidays, this will be >> one of the tickets they get to quickly. >> >> Thanks, >> --Roger >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays@lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
