New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugcheck 167 (invalid SEND request) [CORE5457] #5728
Comments
Commented by: Holger Klemt (klemmo) sample database |
Modified by: Holger Klemt (klemmo)Attachment: BUG.7z [ 13054 ] |
Commented by: @hvlad Simplified test case >isql BUG.FDB -user sysdba
===================== ===================== SQL>
===================== ===================== SQL> commit;
===================== ===================== |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.2 [ 10785 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Commented by: @pavel-zotov It seems that fix works only in 3.0.2 but not in 4.0. On WI-V3.0.2.32683 (07-feb-2017) it works OK. On WI-T4.0.0.522 (03-feb-2017) and WI-T4.0.0.530 (07-feb-2017) it raises:select count(*), sum(val) from test;
|
Modified by: @pavel-zotovAttachment: c5457-1.sql.7z [ 13066 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Waiting for reply on issue 07-feb-2017 1015. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Waiting for reply on issue 07-feb-2017 1015. => Waiting for reply on issue 07-feb-2017 07:15 |
Commented by: @dyemanov I cannot reproduce the crash. Tried v4 embedded and superserver, debug and release builds. I prefixed that script with the CREATE DATABASE command. |
Commented by: @pavel-zotov I've issued command 'create database ...' outside from ISQL, i.e. in the OS command prompt + piping. (May be it's because my FM is 32 bit and is working on Win XP ?..) |
Modified by: @pavel-zotovAttachment: c5457-crash.png [ 13067 ] |
Commented by: @pavel-zotov PS. Changed parameters in firebird.conf: C:\MIX\firebird\QA\fbt-repo\tmp>findstr /r /c:"^[^#;]" C:\MIX\firebird\fb40\firebird.conf | sort |
Commented by: @pavel-zotov > (May be it's because my FM is 32 bit and is working on Win XP ?..) Looks unreal but seems it's indeed like this. Enigma... :-/ |
Commented by: @hvlad I confirm crash of 32-bit embedded release build. No crash in debug build. |
Modified by: @dyemanovsummary: internal Firebird consistency check (invalid SEND request (167), file: JrdStatement.cpp line: 325) => Bugcheck 167 (invalid SEND request) |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done successfully Test Details: Waiting for reply on issue 07-feb-2017 07:15 => |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Holger Klemt (klemmo)
Attachments:
BUG.7z
c5457-1.sql.7z
c5457-crash.png
i have a reproducable bug in fb301 but at the moment i can only reproduce it using ibexpert
(but there is is easy to reproduce and results in the following log entry and all connections
are disconnected, also connections from isql which did not do anything in the mean time)
HKNB6 Mon Jan 16 17:38:54 2017
Modifying procedure CALC_VAL which is currently in use by active user requests
HKNB6 Mon Jan 16 17:39:03 2017
Database: C:\DB\BUG.FDB
internal Firebird consistency check (invalid SEND request (167), file: JrdStatement.cpp line: 325)
i set the transaction setting in ibexpert as follows
isc_tpb_read_committed
isc_tpb_rec_version
isc_tpb_wait
attached database is used, but i can reproduce the error also on another very big database
1. step: open the table tbl in table editor and open data page
2. leave it open
3. change sourcecode of procedure calc_val (for example change the multiplication factor)
4. recompile procedure
5. go back to table tbl data page
6. commit transaction to refresh data
7. this error message will come
internal Firebird consistency check (invalid SEND request (167), file: JrdStatement.cpp line: 325)
the calc_val procedure is used for computed by column
Commits: 5dd8daf 214921b 3e15291 cebbbf5 2cb8c9c 37e2aa3
The text was updated successfully, but these errors were encountered: