[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

To: Simon Majou <simon@majou.org>, openldap-technical@openldap.org
Subject: Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?
From: Howard Chu <hyc@symas.com>
Date: Tue, 18 Aug 2015 12:58:17 +0100
In-reply-to: <CAEoZr1kp0EyTwnO303PDVEGnh+f2sHP_9GrZ__=JXYyNRYEa1Q@mail.gmail.com>
References: <CAEoZr1kp0EyTwnO303PDVEGnh+f2sHP_9GrZ__=JXYyNRYEa1Q@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 SeaMonkey/2.37a1

Simon Majou wrote:

Hello,

I wonder, why do I get a Segmentation fault when I use mdb_put with
MDB_RESERVE on a key that already exists ?


Have no idea. Provide some more details and maybe we can guess.

LMDB version? stack trace from SEGV? What's the size of the existing record,what's the size of the new record? Show sample code that demonstrates the problem?


--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Follow-Ups:
- Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?
  - From: Simon Majou <simon@majou.org>

References:
- Segmentation fault when overwriting a k/v with MDB_RESERVE ?
  - From: Simon Majou <simon@majou.org>

Prev by Date: Segmentation fault when overwriting a k/v with MDB_RESERVE ?
Next by Date: Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?
Index(es):
- Chronological
- Thread