[tor-bugs] #15901 [Tor]: apparent memory corruption -- very difficult to isolate

[Tor Bug Tracker & Wiki]

#15901: apparent memory corruption -- very difficult to isolate
---------------------------+--------------------------------
     Reporter:  starlight  |      Owner:
         Type:  defect     |     Status:  new
     Priority:  critical   |  Milestone:  Tor: 0.2.7.x-final
    Component:  Tor        |    Version:  Tor: 0.2.6.10
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |
---------------------------+--------------------------------

Comment (by someone_else):

 The 'unparsable-desc' file is written when the consensus document can't be
 parsed. In many cases, the corruption will probably still allow the file
 to be parsed and you only get the signature error.

 'unparsable-desc' will have the consensus document from the point of the
 parsing error till the end of the document. The file you attached to the
 bug corresponds to '2015-04-06-03-00-00-consensus'. A tarball with the
 archived consensus docs is available here:
 https://collector.torproject.org/archive/relay-
 descriptors/consensuses/consensuses-2015-04.tar.xz

 This is the error:
 {{{
 < r Unnamed rHlP4BZR0IGz1QovA1SCpKq7RjI pZlK1ZidWxoxe/ec49ZGhy8ekjI
 2015-04-05 16:43:39 83.251.83.140 9001 9030
 ---
 > r Unnamed rHlP4BZR0IGz1QovA1SCpKq7RjI pZlK1ZidWxoxe/ec49ZGhy8ekjI
 2015-04-05 16:-06 01:2.251.83.140 9001 9030
 }}}

 At the end of the consenses document is a list of dir auth signatures (you
 may be able to find them in your core dumps). You can grep for one of the
 lines after '-----BEGIN SIGNATURE-----' against the consensus document
 collection from
 https://collector.torproject.org/archive/relay-descriptors/consensuses
 to find the original one.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15901#comment:34>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online