Trace configuration is not validated on session start
-----------------------------------------------------
Key: CORE-6075
URL: http://tracker.firebirdsql.org/browse/CORE-6075
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.4
Reporter: Pavel Cisar
Priority: Critical
The trace configuration that is part of "start trace" API call is not
parsed/validated on input. The configuration is parsed when other attachment
will have something to trace and detect new trace session. At this point it's
too late to report it correctly to the user. As this is not even logged in
firebird.log, the final result is that all configuration errors are swallowed
and trace produces no output.
Making an error (typo, missing parenthesis or other) in configuration is easy.
User can even mistakenly send (correct because previously tested and working)
configuration in Firebird 2.5 format to the Firebird 3.0. As engine just
happily starts the trace session that does not report anything wrong at any
time and just produces nothing, it could easily lead to deep frustration in
search for cause of the problem. The issue is that configuration is NOT
validated on input (start trace session request). Engine should validate it and
refuse to start the trace session with good error description where the problem
is.
This was verified on 3.0.4, but almost certainly affects all versions since 2.5
up to 4.0 beta 1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
