From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Imap bug after new date libs
Date: Tue, 11 Aug 2020 15:26:31 -0700 [thread overview]
Message-ID: <B5210BC989F0B5831CB5E2CB4CC67062@eigenstate.org> (raw)
In-Reply-To: <24E1197B54F67C5680E6D1DA3F7D9B89@eigenstate.org>
>> Hello all,
>>
>> since ori's new date library the imap4d breaks.
>>
>> The error in /sys/log/imap4d is:
>>
>> imap4d 37122: suicide: sys: trap: fault read addr=0x95 pc=0x2194a7
>>
>> I'll try to fix that bug and the date bug (see other mails) when I have the time. For now I rolled back to the previous version via hg.
>>
>> sirjofri
>
> Hm -- I had avoided committing to imap4d because I haven't
> tested it enough -- is this with or without the patch that
> I sent you?
>
> Can you get the stack trace? you should be able to connect
> to the dead process with acid and run lstk() to get the
> stack trace.
>
> acid 37122
> acid: lstk()
> <stack trace>
Tested a bit -- can't reproduce the crash here, but there *is*
a bug in the uncommitted imap4d changes.
prev parent reply other threads:[~2020-08-11 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 21:05 sirjofri+ml-9front
2020-08-11 21:40 ` [9front] " ori
2020-08-11 22:26 ` ori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B5210BC989F0B5831CB5E2CB4CC67062@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).