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

Re: [tor-bugs] #25957 [Core Tor/Tor]: Tor 0.3.3.5-rc died: Caught signal 11

#25957: Tor 0.3.3.5-rc died: Caught signal 11
--------------------------------------+------------------------------------
 Reporter:  Pine64ARMv8               |          Owner:  (none)
     Type:  defect                    |         Status:  needs_information
 Priority:  Medium                    |      Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor              |        Version:  Tor: 0.3.3.5-rc
 Severity:  Normal                    |     Resolution:
 Keywords:  crash, openssl, 033-must  |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+------------------------------------

Comment (by cypherpunks):

 https://stackoverflow.com/questions/22051294/malloc-segmentation-fault
 > A SIGSEGV (segmentation fault) is firing in malloc is usually caused by
 heap corruption. Heap corruption does not cause a segmentation fault, so
 you would see that only when malloc tries to access there. **The problem
 is that the code that creates the heap corruption could be in any point
 even far away from where the malloc is called.** It is usually the next-
 block pointer inside the malloc that is changed by your heap corruption to
 an invalid address, so that when you call malloc an invalid pointer gets
 dereferenced and you get a segmentation fault.

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