Ryan Tandy writes:
> With your coredump, could you dig a little further into the two
> "sml_mod" structures and show their sm_desc/sm_values/sm_nvalues?
Sure:
(gdb) p *modlist->sml_mod.sm_desc
$8 = {ad_next = 0x0, ad_type = 0x5652a198da20, ad_cname = {bv_len = 3, bv_val =
0x5652a198d900
On Thu, Dec 19, 2019 at 06:12:05PM +0100, wf...@niif.hu wrote:
One and a half year later, and I've got a core dump!
Yay!
I guess the problem here is the "sml_next" value. I have not reproduced
the crash yet, but for a start I am looking at "m2" on syncrepl.c:3236.
With your coredump, could
Control: tag -1 - moreinfo
On Wed, 11 Apr 2018 10:08:25 -0700 Ryan Tandy wrote:
> On Wed, Apr 11, 2018 at 06:41:08PM +0200, Ferenc Wágner wrote:
>
>> slapd[4515]: segfault at 4c ip 7f71abdbfc9b sp 7f716f184780 error 4
>> in back_mdb-2.4.so.2.10.7[7f71abdb+39000]
>
> Not familiar
Control: tag -1 moreinfo
Hello Ferenc,
On Wed, Apr 11, 2018 at 06:41:08PM +0200, Ferenc Wágner wrote:
Does this ring any bells? This crash does not happen frequently, so I
decided to report this little info now, but I'll add more as I got any.
Not familiar to me, nor to upstream based on
Package: slapd
Version: 2.4.44+dfsg-5+deb9u1
Severity: normal
Dear Maintainer,
A partial replica slave crashed with
Apr 3 14:53:51 birch kernel: [1906479.552078] slapd[4515]: segfault at 4c ip
7f71abdbfc9b sp 7f716f184780 error 4 in
back_mdb-2.4.so.2.10.7[7f71abdb+39000]
5 matches
Mail list logo
