[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9987 [Tor]: Bug in mp_pool_get()

#9987: Bug in mp_pool_get()
-----------------------------+------------------------------------
     Reporter:  tmpname0901  |      Owner:
         Type:  defect       |     Status:  new
     Priority:  major        |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor          |    Version:  Tor: 0.2.4.17-rc
   Resolution:               |   Keywords:  024-backport tor-relay
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------------------
Changes (by nickm):

 * keywords:   => 024-backport tor-relay
 * milestone:  Tor: 0.2.4.x-final => Tor: 0.2.5.x-final


Comment:

 There isn't enough information here to figure this one out.  Is there any
 chance of a stack trace?  Does this happen repeatedly?  Otherwise, it's
 not clear to me how this can happen.

 I wonder if we could do anything about this, if it's a memory corruption
 thing.  Maybe we can make a configure option to use malloc instead of
 memory pools, and run under valgrind?    Maybe we can have an option
 canaries at the start and end of chunks?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9987#comment:1>
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