Re: PR_ASSERT problem

[Carsten Grzemba <grzemba@xxxxxxxxxxxx>]

On 28.09.17 00:49, William Brown  <wibrown@xxxxxxxxxx> wrote:

On Wed, 2017-09-20 at 14:30 +0200, Carsten Grzemba wrote:
> my build on OpenIndiana with the IllumOS provided NSPR cores on startup of some commands:
>
> $ pwdhash
> Assertion failure: 0 == lock->notified.length, at /jenkins/jobs/oi-userland/workspace/components/library/mozilla-nspr/nspr-4.12/nspr/pr/src/pthreads/ptsynch.c:159
> /usr/bin/pwdhash: line 60: 5993: Abort(coredump)
>
> $ pstack core
> core 'core' of 5993: /usr/bin/amd64/pwdhash-bin
>  fffffd7fff2b4eda _lwp_kill () + a
>  fffffd7fff2480e0 raise (6) + 20
>  fffffd7fff220818 abort () + 98
>  fffffd7ff943fda2 ???????? ()
>  fffffd7ff9457828 PR_DestroyLock () + d8
>  fffffd7ff978bc2a slapi_entry_free () + 11a
>  0000000000402888 init_config () + 2d8
>  0000000000402d43 main () + 353
>  000000000040235c _start () + 6c
>
> Before I dive in the source code, has anyone a hint where I can start to search what happens here?
> <signaturebeforequotedtext></signaturebeforequotedtext><signatureafterquotedtext></signatureafterquotedtext>

Sounds like the lock may not have been created properly? Sadly I think
you need to dive into the source,

:(

Let me know if you need any other advice.

It works, if I compile with 

  AC_DEFINE([USE_POSIX_RWLOCKS], [1], [POSIX rwlocks])

Because this is also set in Linux, I guess the NSPR Threads is not tested anymore.
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx