Den sön 9 aug. 2020 kl 15:28 skrev Daniel Sahlberg <
daniel.l.sahlberg_at_gmail.com>:
> Den sön 9 aug. 2020 15:14Nathan Hartman <hartman.nathan_at_gmail.com> skrev:
>
>> On Sat, Aug 8, 2020 at 1:23 PM James McCoy <jamessan_at_jamessan.com> wrote:
>>
>>> On Sat, Aug 08, 2020 at 10:35:14AM -0400, James McCoy wrote:
>>> > The Debian builds for 1.14.0 recently started crashing while running
>>> the
>>> > Java tests. This is pretty far out of my expertise, so hopefully
>>> > someone can help out.
>>
>>
>> I don't know if it's related, but a few days ago we received a patch from
>> Alexandr Miloslavskiy to fix a crash which is caused by a garbage collected
>> object not being pinned before use by native code [1]. Perhaps Alexandr
>> found the issue because of a similar crash to the one you're experiencing.
>> Could you try the patch?
>>
>
> I thought about the same. However the patch didn't seem to make a
> difference.
>
> I can confirm James' statement that it crashes when compiled using GCC 10
> but it seems to work with GCC 9. In my case I'm using Fedora 32 versus
> Fedora 30 so I can't rule out that there are other differences but it seems
> reasonable that GCC is doing something strange.
>
> I have some done some preliminary investigations but I'm done yet, it
> seems that the code is using an object that has already been destructed.
>
> Kind regards
> Daniel
>
I have investigated further and I think I have found the issue. A patch is
attached, basically changing
const String::Contents key(String(m_env, jkey));
to
const String str(m_env, jkey);
const String::Contents key(str);
in ImmutableMap.for_each.
If I understand things correctly (admittedly I'm not an expert in C++), the
lifetime of the String object is just the execution of the constructor of
the Contents class. But the Contents class saves a reference to the String
object in a member variable. When the Contents object is destroyed at the
end of the function, it references the already previously destroyed String
object.
This is the same in GCC 9 as well as GCC 10 (also the same in Visual Studio
2019!) so I'm guessing that GCC 10 is better at "cleaing up" destroyed
object to the point where it trigger a segfault (but it's not consistent as
a "minimal example" with GCC 10 show this behaviour but still doesn't
segfault).
When the String object is assigned to it's own variable it lives until the
end of the function and it is destroyed after the Contents object, thus the
destructor of the Contents class succeeds.
With this patch make check-javahl succeeds with GCC 10. I have also applied
it in my GCC 9 build and all checks still succeed.
Kind regards
Daniel
Received on 2020-08-09 23:10:24 CEST