Issues with debugging GC-related crashes #2
Matthias Klumpp
mak at debian.org
Wed Apr 18 22:19:33 UTC 2018
On Wednesday, 18 April 2018 at 20:36:03 UTC, Johannes Pfau wrote:
> [...]
>
> Actually this sounds very familiar:
> https://github.com/D-Programming-GDC/GDC/pull/236
>
> it took us quite some time to reduce and debug this:
>
> https://github.com/D-Programming-GDC/GDC/pull/236/commits/
> 5021b8d031fcacac52ee43d83508a5d2856606cd
>
> So I wondered why I couldn't find this in the upstream druntime
> code. Turns out our pull request has never been merged....
>
> https://github.com/dlang/druntime/pull/1678
Just to be sure, I applied your patch, but unfortunately I still
get the same result...
On Wednesday, 18 April 2018 at 20:38:20 UTC, negi wrote:
> On Monday, 16 April 2018 at 16:36:48 UTC, Matthias Klumpp wrote:
>> ...
>
> This reminds me of (otherwise unrelated) problems I had
> involving Linux 4.15.
>
> If you feel out of ideas, I suggest you take a look at the
> kernels. It might
> be that Ubuntu is turning some security-related knob in a
> different direction
> than Debian. Or it might be some bug in 4.15 (I found it to be
> quite buggy,
> specially during the first few point releases; 4.15 was the
> first upstream
> release including large amounts of meltdown/spectre-related
> work).
All the crashes are happening on a 4.4 kernel though... I am
currently pondering digging out a 4.4 kernel here to see if that
makes me reproduce the crash locally.
More information about the Digitalmars-d
mailing list