Unity tests crashes when compiling google-mocks with gcc-6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
google-mock (Debian) |
Fix Released
|
Unknown
|
|||
google-mock (Ubuntu) |
Fix Released
|
Critical
|
Marco Trevisan (Treviño) |
Bug Description
Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash.
Starting program: /tmp/unity-
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
[New Thread 0x7fffe0f1d700 (LWP 22778)]
[New Thread 0x7fffdbfff700 (LWP 22779)]
[New Thread 0x7fffdb7fe700 (LWP 22780)]
[==========] Running 1637 tests from 105 test cases.
[----------] Global test environment set-up.
[----------] 14 tests from TestActionLink
[ RUN ] TestActionLink.
Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault.
testing:
at /usr/include/
1530 this->UntypedIn
#0 testing:
at /usr/include/
No locals.
#1 testing:
No locals.
#2 unity::
No locals.
#3 0x00005555559ce574 in unity::
at /tmp/unity-
No locals.
#4 0x00005555559d53bf in std::function<bool (unity:
No locals.
#5 nux::RWProperty
at /usr/include/
No locals.
#6 0x00005555559d0c31 in unity::
at /tmp/unity-
A fix is available at https:/
Changed in google-mock (Debian): | |
status: | Unknown → Fix Committed |
Changed in google-mock (Debian): | |
status: | Fix Committed → Fix Released |
Here's the debdiff for fixing the ubuntu package