[tor-bugs] #17808 [Core Tor/Tor]: Tor 0.2.7.6 doesn't produce a backtrace on gcc 4.9.3 on OS X 10.11.2

[Tor Bug Tracker & Wiki]

#17808: Tor 0.2.7.6 doesn't produce a backtrace on gcc 4.9.3 on OS X 10.11.2
---------------------------------------+-----------------------------------
 Reporter:  teor                       |          Owner:
     Type:  defect                     |         Status:  needs_information
 Priority:  Medium                     |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor               |        Version:  Tor: 0.2.7.6
 Severity:  Normal                     |     Resolution:
 Keywords:  tor-03-unspecified-201612  |  Actual Points:
Parent ID:                             |         Points:  ?large?
 Reviewer:                             |        Sponsor:
---------------------------------------+-----------------------------------

Comment (by teor):

 Replying to [comment:6 nickm]:
 > This seems to be compiler-dependent and library-dependent, and not have
 much to do with Tor's actual behavior or use of backtrace.  I'm putting
 this in needs_information to get this information:
 >    * Which compiler and version?  Which OS and version?

 gcc 4.9, 5, 6 on macOS 10.11 - 10.12 on x86_64
 (clang and gcc i386 are not affected)

 >    * Is this or is this not a regression?

 Unlikely, because the default compiler on macOS has been clang for ages.

 >    * What is the output in each case?

 {{{
 BAD
 Feb 24 13:20:34.917 [err] tor_assertion_failed_(): Bug:
 src/test/test_bt_cl.c:43: crash: Assertion 1 == 0 failed; aborting. (on
 Tor 0.3.1.0-alpha-dev efa5bbaba07d20d1)
 Feb 24 13:20:34.917 [err] Bug: Assertion 1 == 0 failed in crash at
 src/test/test_bt_cl.c:43. Stack trace: (on Tor 0.3.1.0-alpha-dev
 efa5bbaba07d20d1)
 Feb 24 13:20:34.917 [err] Bug:     0   test-bt-cl
 0x00000001038d63c4 log_backtrace + 68 (on Tor 0.3.1.0-alpha-dev
 efa5bbaba07d20d1)
 BAD

 ============================================================ T= 1487902834
 Tor died: Caught signal 11
 0   test-bt-cl                          0x000000010e4b42aa crash_handler +
 58
 1   ???                                 0x0000000000000130 0x0 + 304
 -158318
 Exit 1
 }}}

 > The best solution for the meantime I can find is to treat this failure
 as a "SKIP" on FreeBSD.

 macOS still suffers from this, but we can't skip the entire platform,
 because clang and i386 both work fine.

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