Community
Participate
Working Groups
The ImportTraceWizard performs insufficient verification before allowing importation of a trace in a trace project. To reproduce: - Delete/rename a parsing library (say liblttvtraceread-2.6) - Start LTTng and import a trace of that format (2.6) The trace will be imported in the project but an exception will be thrown (or error dialog opened) when trying to open it.
Created attachment 202520 [details] Missing parsing library error dialog
Created attachment 202521 [details] Unrecognized trace type
Created attachment 202523 [details] Unsupported trace version error dialog
With the possibility of changing dynamically the parsing trace library path, it becomes undecidable if a trace can or can't be imported in a given project. The current behavior is to perform this validation when opening the trace and to display the appropriate error dialog (see attachments) if an error occurs. This should be enough.
Closing bug.