Submitted by: Thomas Steinmaurer (tsteinmaurer)

I have a reproducable server crash with the Trace API here:

Windows XP Prof.
Firebird 2.5 Snapshot Build 25920 - SuperClassic

The following user trace configuration is used:

<database tourism.fdb>
enabled true
log_connections true
log_transactions true
log_statement_prepare true
log_statement_free true
log_statement_start true
log_statement_finish true
log_procedure_start true
log_procedure_finish true
log_trigger_start true
log_trigger_finish true
log_context true
print_plan true
print_perf true
log_blr_requests true
print_blr true
log_dyn_requests true
print_dyn true
</database>
<services>
</services>

Usage:

fbtracemgr.exe -se localhost/3051:service_mgr -user sysdba -password masterkey -start -name "My Trace" -config trace.conf

Now, in isql:

select * From customer;

works fine. I get a result set in isql and the trace output is written to stdout. Now, executing a syntactical wrong statement, e.g.:

select customer;

In both sesssions, isql and trace output, I get an unable to complete network request to host "localhost" error message.

In isql:

Statement failed, SQLCODE = 08006
Unable to complete network request to host "localhost".
-Error reading data from the connection.

In trace output:
Unable to complete network request to host "localhost".
-Error reading data from the connection.

If there is no trace session running, isql complains about the wrong SQL statement and the server is keep on running.

Commits: b9012c8 b3a3268