core dump in stored procedure using execute statement [CORE921] #1319
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff Bug was due to very rarely happening BOF when reading data in memcpy(). I.e. it happened not due to overwritten memory, but due to reading out of allocated to process address space. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0 RC5 [ 10071 ] |
Modified by: @dyemanovFix Version: 1.5.4 [ 10100 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 11193 ] => Firebird [ 15229 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Not enough information |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Frank Schlottmann-Goedde (fsg)
#0 0x4042e58c in memcpy () from /lib/tls/libc.so.6
#1 0x400ec721 in ExecuteStatement::Fetch (this=0x41fbb3bc, tdbb=0xbfd05f70, JrdVar=0x41a21484) at ../src/jrd/execute_statement.cpp:242
#2 0x400e73e3 in looper (tdbb=0xbfd05f70, request=0x413da6d8, in_node=0x41a2146c) at ../src/jrd/exe.cpp:2327
#3 0x400e5fa8 in execute_looper (tdbb=0xbfd05f70, request=0x413da6d8, transaction=0x409a91d8, next_state=1094610824)
at ../src/jrd/exe.cpp:1251
...
(gdb) frame 1
#1 0x400ec721 in ExecuteStatement::Fetch (this=0x41fbb3bc, tdbb=0xbfd05f70,
JrdVar=0x41a21484) at ../src/jrd/execute_statement.cpp:242
242 memcpy(d->dsc_address, var->sqldata, length);
Current language: auto; currently c++
(gdb) print d
$1 = (dsc *) 0x413e2cac
(gdb) print *d
$2 = {dsc_dtype = 3 '\003', dsc_scale = 0 '\0', dsc_length = 16002,
dsc_sub_type = 21, dsc_flags = 0, dsc_address = 0x41fb817a "$"}
(gdb) print var->sqldata
$3 = 0x41ff8dbc "$"
(gdb) print length
$4 = -24464
Commits: b7cb426 42d675f f44fd54
The text was updated successfully, but these errors were encountered: