-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation warning in db/undo_database.hpp:69:22: throw will always call terminate() #1237
Comments
The portion of the log you show contains only a warning, and should not stop the compilation from completing. Please provide the entire compilation log. As it is probably large, I recommend posting it to a site like http://pastebin.com and then posting the link to it here in this issue. |
Thank you. Can you capture all of the output of the make command? Something like:
and then provide a link to |
https://github.com/cogutvalera/bitshares-logs/blob/master/compile.log now I don't see the warning I've told about, do you know why ? or maybe should I cleanup and reset everything and after that re-compile the whole project again ? |
The problem is that the destructor of undo_db can throw under certain circumstances. This is bad practice - destructors shouldn't ever throw. It's not really a problem for us, because undo_db has the same lifetime as the application itself. |
I see that #1194 was closed already. Does that fix this? I see @cogutvalera build from |
No, #1194 is unrelated |
@cogutvalera were you able to find the error that prevented you from compiling? Please post it here. If you reset your project and the problem went away, please let us know and close this ticket. Thanks. |
@jmjatlanta that wasn't error, that was warning, I think we don't need even compile warnings, right ? here is my compile.log file, I still see that warning |
I'm sorry. I misinterpreted the original post. I thought the compilation was failing. There is another similar (albeit harder to fix) warning in FC. I created #1246 to fix those warnings before I realized this ticket could be used. Note to self: Get more organized! |
#1246 is somewhat a duplicate of this issue, albeit broader in scope. |
Build Error Description
Build Environment
Steps To Reproduce
Steps to reproduce the behavior (example outlined below):
CORE TEAM TASK LIST
Build Error
Bug Report
The text was updated successfully, but these errors were encountered: