scoperunner segfaults if ScopeBase.start() raises an exception
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-scopes-api |
Fix Released
|
Undecided
|
Michi Henning | ||
unity-scopes-api (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
As a test, I applied the attached patch to the scope-A demo, to make it raise an exception in its start() method.
When I started the scope registry for the demo with:
cd demo
../
I got the following output:
Raising exception from start
scoperegistry: process 14585 terminated by signal 11, command line: /home/james/
If I manually re-ran the scope with the command line given in the error, it printed the "Raising exception from start" message but didn't segfault until I tried running a query via the demo client.
I am testing against revision 102.
Related branches
- Michal Hruby (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 1212 lines (+142/-604)9 files modifiedinclude/scopes/internal/ScopeLoader.h (+3/-35)
src/internal/ScopeLoader.cpp (+91/-376)
test/gtest/scopes/internal/ScopeLoader/BadVersion.cpp (+0/-5)
test/gtest/scopes/internal/ScopeLoader/CMakeLists.txt (+0/-1)
test/gtest/scopes/internal/ScopeLoader/Counters.cpp (+0/-14)
test/gtest/scopes/internal/ScopeLoader/Counters.h (+0/-3)
test/gtest/scopes/internal/ScopeLoader/MyScope.h (+0/-5)
test/gtest/scopes/internal/ScopeLoader/ScopeLoader_test.cpp (+48/-105)
test/gtest/scopes/internal/ScopeLoader/ThrowUnityExFromRun.cpp (+0/-60)
Changed in unity-scopes-api: | |
status: | New → Fix Committed |
Changed in unity-scopes-api: | |
status: | Fix Committed → In Progress |
Changed in unity-scopes-api: | |
status: | Fix Committed → Fix Released |
backtrace of scoperunner after the crash.