Recent regression causing confparse error
|Reported by:||atagar||Owned by:|
Hi Nick. For a few weeks now our jenkins tests for stem/tor integration have been busted. Turns out that they caught our first tor bug, yay!
I did a bisect and narrowed the regression to the merge on 5/28 of commit d3125a3...
2613c98 bad (6/16/13) 7159e19 bad (6/5/13) 4d7ac69 bad (5/29/13) 97d1caa bad (5/28/13) d3125a3 just plain busted (fixed in the next commit) e7134c2 good (5/24/13) cb488f9 good (5/20/13)
To repro the issue kick off a tor instance then issue an invalid LOADCONF. Here's an example...
% telnet localhost 9051 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. AUTHENTICATE 250 OK +LOADCONF ContactInfo confloaded . Connection closed by foreign host.
Tor will fail with...
Jun 23 13:03:25.000 [err] config_is_same(): Bug: src/or/confparse.c:983: config_is_same: Assertion fmt && o2 failed; aborting. src/or/confparse.c:983 config_is_same: Assertion fmt && o2 failed; aborting.
Change History (8)
comment:2 Changed 4 years ago by nickm
- Keywords tor-client 023-backport added
- Milestone set to Tor: 0.2.4.x-final
- Status changed from new to needs_review
comment:4 Changed 4 years ago by nickm
- Milestone changed from Tor: 0.2.4.x-final to Tor: 0.2.3.x-final