On 03/21/2014 03:49 PM, Carsten Schoenert wrote: > it's some time gone after this mail from you. The current Icedove > version 24.3.0-2 has a fixed LDFLAGS variable. We had include > '-Wl,--as-needed' which broke libraries dependencies while linking. So > maybe theese crashes are also possibly gone.
alas, no. I had a segfault crash again earlier today, with 24.3.0-2 :(
> On the other hand the code line and function that shown in the gdb logs
> are from the nspr thing and normaly should't depend on the fixed linker
> option I think.
>
> mozilla/nsprpub/pr/src/md/unix/uxproces.c
>
> 507 static void
> 508 ProcessReapedChildInternal(pid_t pid, int status)
> 509 {
> 510 pr_PidRecord *pRec;
> 511
> 512 pRec = FindPidTable(pid);
> 513 if (NULL == pRec) {
> 514 pRec = PR_NEW(pr_PidRecord);
> 515 pRec->pid = pid;
> 516 pRec->state = _PR_PID_REAPED;
> 517 pRec->exitStatus = ExtractExitStatus(status);
> 518 pRec->reapedCV = NULL;
> 519 InsertPidTable(pRec);
> 520 } else {
> 521 PR_ASSERT(pRec->state != _PR_PID_REAPED); <----
> 522 if (_PR_PID_DETACHED == pRec->state) {
> 523 PR_ASSERT(NULL == pRec->reapedCV);
> 524 DeletePidTable(pRec);
> 525 PR_DELETE(pRec);
> 526 } else {
> 527 PR_ASSERT(_PR_PID_WAITING == pRec->state);
> 528 PR_ASSERT(NULL != pRec->reapedCV);
> 529 pRec->exitStatus = ExtractExitStatus(status);
> 530 pRec->state = _PR_PID_REAPED;
> 531 PR_NotifyCondVar(pRec->reapedCV);
> 532 }
> 533 }
> 534 }
>
> As far as I can see the PR_ASSERT comes from
> mozilla/nsprpub/pr/include/prlog.h, but this header is for debugging
> stuff.
>
> 206 #define PR_ASSERT(_expr) \
> 207 ((_expr)?((void)0):PR_Assert(# _expr,__FILE__,__LINE__))
I'm not sure what i should do with this information.
I can re-run my MUA under debug mode again for a while if it would be
useful to get another backtrace. would that be helpful? I'm surprised
that I am the only one seeing this. Do other icedove users not have my
mail volume or something? maybe i happen to be talking to servers with
particular bugs? or too many servers concurrently?
If icedove was a simpler program, i think it would be more
straightforward to diagnose; but at the moment, i'm mystified by this
ongoing problem.
--dkg
signature.asc
Description: OpenPGP digital signature
