------------------ Original ------------------
From: "dovecot" https://dovecot.org/mailman/listinfo/dovecot
or, via email, send a message with subject or body 'help' to
dovecot-request@dovecot.org
You can reach the person managing the list at
dovecot-owner@dovecot.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dovecot digest..."
Today's Topics:
1. special characters in FTS Solr fail (piuma@piumalab.org)
2. json_parse_number broken by compiler optimization
(Christian Ehrhardt)
3. Re: json_parse_number broken by compiler optimization (Aki Tuomi)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Mar 2021 16:20:56 +0200
From: "piuma@piumalab.org" https://dovecot.org/pipermail/dovecot/attachments/20210330/08492366/attachment-0001.gz>;
------------------------------
Message: 2
Date: Tue, 30 Mar 2021 17:53:27 +0200
From: Christian Ehrhardt https://launchpadlibrarian.net/529849650/buildlog_ubuntu-hirsute-amd64.dovec...
A coworker tried 2.3.14 but got the same result.
What fails is the json_parser build time test like:
test-json-parser.c:161: Assert(#25) failed:
null_strcmp(json_output[pos].value, value) == 0
I was looking into that a bit more and what I found is that it is
dependent on the new toolchain
of gcc 10.2.0-1.
Not all calls to json_parse_* fail, e.g. the first one looks all good and passes
I was iterating the tests using a report function defined like
(gdb) define repcon
>c
>p pos
>p json_output[pos].type
>p type
>p json_output[pos].value
>p value
>call null_strcmp(json_output[pos].value, value)
>end
The first one to be bad was:
Breakpoint 2, test_json_parser_success (full_size=https://launchpadlibrarian.net/529849650/buildlog_ubuntu-hirsute-amd64.dovec...
> A coworker tried 2.3.14 but got the same result.
>
> What fails is the json_parser build time test like:
> test-json-parser.c:161: Assert(#25) failed:
> null_strcmp(json_output[pos].value, value) == 0
>
> I was looking into that a bit more and what I found is that it is
> dependent on the new toolchain
> of gcc 10.2.0-1.
>
> Not all calls to json_parse_* fail, e.g. the first one looks all good and passes
> I was iterating the tests using a report function defined like
>
> (gdb) define repcon
> >c
> >p pos
> >p json_output[pos].type
> >p type
> >p json_output[pos].value
> >p value
> >call null_strcmp(json_output[pos].value, value)
> >end
>
> The first one to be bad was:
> Breakpoint 2, test_json_parser_success (full_size=https://dovecot.org/mailman/listinfo/dovecot
------------------------------
End of dovecot Digest, Vol 215, Issue 77
****************************************