BIND 10 #1025: logging argument should be more carefully checked
BIND 10 Development
do-not-reply at isc.org
Thu Jul 7 12:09:33 UTC 2011
#1025: logging argument should be more carefully checked
-------------------------------------+-------------------------------------
Reporter: | Owner: vorner
jinmei | Status: reviewing
Type: | Milestone:
defect | Sprint-20110712
Priority: major | Resolution:
Component: | Sensitive: 0
Unclassified | Sub-Project: Core
Keywords: | Estimated Difficulty: 3.0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by stephen):
* owner: stephen => vorner
Comment:
An unhandled bad_lexical_cast exception gives the message:
{{{
terminate called after throwing an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast>
>'
what(): bad lexical cast: source type value could not be interpreted as
target
Aborted
}}}
(That example is from Ubuntu.) Throwing an isc::Exception-derived
exception allows more information to be given as to where the problem
lies. The exception also includes the file and line (and the text of the
message also includes the name of the method in which the exception
arose.)
--
Ticket URL: <http://bind10.isc.org/ticket/1025#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list