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

Output exception details (if available) for troubleshooting #27

Closed
BSipos-RKF opened this Issue Dec 30, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@BSipos-RKF

BSipos-RKF commented Dec 30, 2014

In some cases where a try{} catch{} block is used to call module code and output error text, there is a separate catch for std::exception type to allow printing the exception what() message. In other cases, only a catch-all ... is used.

The specific one I ran into is in src/service/usServiceListeners.cpp within ServiceListeners::ServiceChanged.

@saschazelzer saschazelzer added this to the Release 3.0 milestone Jan 19, 2015

@saschazelzer saschazelzer self-assigned this Jan 19, 2015

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Jan 19, 2015

Member

Thanks, I will check all try/catch blocks and improve the error reporting.

Member

saschazelzer commented Jan 19, 2015

Thanks, I will check all try/catch blocks and improve the error reporting.

saschazelzer added a commit that referenced this issue Aug 10, 2016

Merge branch '27-consistent-exception-detail-messages' into development
Closes #27

# Conflicts:
#	framework/src/bundle/BundlePrivate.cpp
#	framework/src/util/FrameworkEvent.cpp
#	framework/src/util/Utils.cpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment