PerformanceEstimatorPlugin.cpp: comment out destructor to avoid segfault as sim exit#2
Open
PhilippvK wants to merge 1 commit into
Open
PerformanceEstimatorPlugin.cpp: comment out destructor to avoid segfault as sim exit#2PhilippvK wants to merge 1 commit into
PhilippvK wants to merge 1 commit into
Conversation
…ult as sim exit Co-authored-by: Daniel Schloms <daniel.schloms@gmail.com> The following segfault at the end of the simulation (leading to a non-zero exit code) seems to be caused by the destructor. ``` CPU0 exited with exception: 0x80000000: Finished cpu execution. This is the proper way to exit from etiss::CPUCore::execute. [1] 3523153 segmentation fault (core dumped) ./build_dir/installed/bin/bare_etiss_processor ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The following segfault at the end of the simulation (leading to a non-zero exit code) seems to be caused by the destructor.
This is more like a workaround for the actual problem, but ignoring the exit code of etiss is also not acceptable...
@danielschloms