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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#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 starlight):

 Replying to [comment:34 someone_else]:
 > This is the error:
 > {{{
 > < 2015-04-05 16:43:39 83.251.83.140 9001 9030
 > ---
 > > 2015-04-05 16:-06 01:2.251.83.140 9001 9030
 > }}}

 Right, _exactly_ _eight_ _bytes_ corrupted
 in the entire document.  My bet says
 it corresponds with a 64-bit-aligned
 memory address in the core image, just
 like my analysis above of EVENT 05
 (though I will verify it).

 I'm sticking with my theory that an
 memory pointer somewhere is getting
 the low-order 16-bits overwritten.
 This is not a confining theory--limitless
 possible ways for it happen either
 in the zlib code or elsewhere.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15901#comment:36>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs