Hello, that cost me some hairs (*g*) the last days and I only can reproduce it with FB TraceManager and not the trace API command-line tools, but as this happens only against a 2.5.1 server and not 2.5.0, I feel there is something wrong here.
I tested with 2.5.0 and 2.5.1 SuperClassic 64-bit on Win7 Prof. Basically, our product can start trace sessions and queries the list of sessions regularly. The server crash with 2.5.1 happens while fetching the list of trace sessions when there are other trace sessions started. Simply running the trace stuff against 2.5.0 doesn't show any problem. When working against 2.5.1, the crash happens. FB TraceManager is a 32-bit application and ships with 2.5.0 embedded 32-bit and uses that as client library as well. In the tests, both server versions are started as an application with e.g.: fb_inet_server.exe -a -m -i -p 3051 Again. We don't encounter any problems when running against 2.5.0. Running FB TraceManager against 2.5.1 crashes the server. I would love being able to give you a reproduceable test case with the trace api command-line utilities, but I can't. Any pointers are much appreciated, because currently, FBTM can't be used against 2.5.1. Thanks, Thomas ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
