Re: Issue with mdb_cursor_put

Brüns, Stefan wrote: Hi, I see a similar problem as reported in October 2017 for mdb_cursor_del, i.e. pages ending up twice on the dirty list. Backtrace: #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x761c8da1 in __GI_abort () at abort.c:79 #2 0x7ff

Issue with mdb_cursor_put

Hi, I see a similar problem as reported in October 2017 for mdb_cursor_del, i.e. pages ending up twice on the dirty list. Backtrace: #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x761c8da1 in __GI_abort () at abort.c:79 #2 0x75a31052 in mdb_asser