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

Re: ordered indexing for integers

To: Howard Chu <hyc@symas.com>
Subject: Re: ordered indexing for integers
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Sat, 1 Dec 2007 19:28:42 +0100
Cc: OpenLDAP-devel@openldap.org
In-reply-to: <4751A1B1.50500@symas.com>
References: <4742F5EE.5070100@symas.com> <hbf.20071130al9x@bombur.uio.no> <hbf.20071130be5u@bombur.uio.no> <47504610.9050607@symas.com> <475080B3.8020505@symas.com> <hbf.20071201n2xi@bombur.uio.no> <47513544.4000601@symas.com> <hbf.20071201ce7q@bombur.uio.no> <4751A1B1.50500@symas.com>

Howard Chu writes:
>Hallvard B Furuseth wrote:
>> Got crashes due to a write after 'tmp', incremented size by 1.
>> Haven't looked at why yet, or whether that's the complete fix.
>
> That should never happen. Do you have the backtrace from when the
> write occurred?

No, got memory corruption later.  Valgrind pointed out the tmp write,
but I don't see in the doc how to get valgrind to core at first error.

-- 
Regards,
Hallvard

Follow-Ups:
- Re: ordered indexing for integers
  - From: Howard Chu <hyc@symas.com>
- Re: ordered indexing for integers
  - From: Howard Chu <hyc@symas.com>

References:
- Re: ordered indexing for integers
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: ordered indexing for integers
  - From: Howard Chu <hyc@symas.com>
- Re: ordered indexing for integers
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: ordered indexing for integers
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: Empty DN ("") String Value?
Next by Date: Re: ordered indexing for integers
Index(es):
- Chronological
- Thread