|
Hello dear forum, Today I have installed the new version of SA (17.0.6.2757 SP 1), and I found out that it is possible to crash dbsrv17.exe (64-bit) with the SQL Profiler, if you choose the option as you see in the image below:
To reproduce this, please follow steps:
My purpose was to trace all SQL statements that have the specific table name (I was trying to capture what the application is doing with the DB). I have already submitted two crash reports, but I'd like to hear from you, whether you have the same behavior. p.s. maybe this isn't a bug, but a feature. Thanks, |
|
This definitely is bug, not a "feature". We'll look into it. -- Chris Irie (SQL Anywhere engineering) Thank you, Chris. If you will update the thread with the results, it will be super!
(20 Dec '16, 11:56)
Vlad
1
I was able to reproduce it. Your instructions were very clear and easy to follow. -- Chris
(20 Dec '16, 13:09)
ChrisIrie
|
Ah yes, something to add to the list of reproducible actions to crash the database server, as created by Reimer:
How to crash a SA11 engine with a simple SQL statement
(although here it's no simple SQL statement, apparently...)
And a nice way to introduce 17.0.6 - I wasn't aware of that:)
(Studying the readme it seems that one has not the same number of new features as 17.0.4...)
I forgot to mention, even with an empty DB, one can crash the process. Do you have a chance to check my steps?
Sorry, not currently... - I have not yet installed the EBF:(