https://bugs.openldap.org/show_bug.cgi?id=9626
--- Comment #2 from Howard Chu <[email protected]> --- (In reply to carlos.velasco from comment #1) > It seems ids get corrupted. > > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f2a32a4109f in mdb_midl_append_list (idp=0x7f29f8041b13, > app=0x25fa538) at midl.c:175 > 175 if (ids[0] + app[0] >= ids[-1]) { > [Current thread is 1 (Thread 0x7f2a09ffb640 (LWP 204177))] > (gdb) bt > #0 0x00007f2a32a4109f in mdb_midl_append_list (idp=0x7f29f8041b13, > app=0x25fa538) at midl.c:175 > #1 0x00007f2a32a325bf in mdb_txn_commit (txn=0xf9bda0) at mdb.c:3485 In frame 1 can you get the output for: info locals print *txn print *parent Does your code actually use nested transactions? > #2 0x00007f2a32eb8904 in > modsecurity::collection::backend::LMDB::storeOrUpdateFirst (this=0x1fe28b0, > key=..., value=...) at collection/backend/lmdb.cc:245 > #3 0x00007f2a32e97bb8 in > modsecurity::collection::Collection::storeOrUpdateFirst (value=..., > compartment2=..., compartment=..., key=..., this=0x1fe28b0) at > ../headers/modsecurity/collection/collection.h:99 > #4 modsecurity::variables::Ip_DynamicElement::storeOrUpdateFirst > (value=..., var=..., t=<optimized out>) at ../src/variables/ip.h:110 > #5 modsecurity::actions::SetVar::evaluate (this=0x30acfc0, rule=<optimized > out>, t=<optimized out>) at actions/set_var.cc:144 > #6 0x00007f2a32e641bc in > modsecurity::RuleWithActions::executeActionsIndependentOfChainedRuleResult > (this=this@entry=0x30c9f50, trans=trans@entry=0x7f29f8036e40, > containsBlock=containsBlock@entry=0x7f2a09ff94ef, ruleMessage=...) at > rule_with_actions.cc:199 > #7 0x00007f2a32e6dc33 in modsecurity::RuleWithOperator::evaluate > (this=<optimized out>, trans=<optimized out>, ruleMessage=...) at > /usr/include/c++/11.2.0/ext/atomicity.h:109 > #8 0x00007f2a32e66e59 in modsecurity::RuleWithActions::evaluate > (this=0x30c9f50, transaction=0x7f29f8036e40) at > /usr/include/c++/11.2.0/ext/atomicity.h:111 > #9 0x00007f2a32e5cd3c in modsecurity::RulesSet::evaluate (this=<optimized > out>, phase=phase@entry=3, t=t@entry=0x7f29f8036e40) at rules_set.cc:210 > #10 0x00007f2a32e41793 in modsecurity::Transaction::processRequestBody > (this=0x7f29f8036e40) at transaction.cc:942 > #11 0x00007f2a32fa0a28 in hook_request_late () from > /usr/lib64/httpd/modules/mod_security3.so > #12 0x000000000045616b in ap_process_request_internal () > #13 0x0000000000476ef3 in ap_process_async_request () > #14 0x0000000000473150 in ap_process_http_connection () > #15 0x00000000004695bf in ap_run_process_connection () > #16 0x00007f2a33492831 in process_socket () from > /usr/lib64/httpd/modules/mod_mpm_event.so > #17 0x00007f2a33493307 in worker_thread () from > /usr/lib64/httpd/modules/mod_mpm_event.so > #18 0x00007f2a33703fd6 in start_thread () from /lib64/libpthread.so.0 > #19 0x00007f2a336241df in clone () from /lib64/libc.so.6 > (gdb) print ids > $1 = (MDB_IDL) 0x7069746c756d7c20 > (gdb) print ids[0] > Cannot access memory at address 0x7069746c756d7c20 -- You are receiving this mail because: You are on the CC list for the issue.
