25.05.2016 18:52, Dmitry Yemanov wrote: > Here is sequence of savepoints generated in this test: >> >> >>Request to rollback to 11. Stack is 14->11->5->10->1-> >> >>Request to rollback to 10. Stack is 5->10->1->
I tried to fix that by reusing savepoints started by looper. For that I added req_savepoints to request and in looper I store savepoint there after merging it the same way as SP savepoints are stored in req_proc_sav_point. So far so good, savepoints stack in test case become right. But build started to crash because some requests live longer than transaction (which is well-known) and the pointer to stored savepoints, allocated from transaction pool become invalid. It was expected and I put call to Savepoint::destroy() to EXE_unwind() along with releasing of req_proc_sav_point. But it still crash. Where is a right place to release stored savepoints? Why releasing of savepoints from SP don't crash? -- WBR, SD. ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
