Closed zboszor closed 1 year ago
How very odd. No I don't really know I am afraid. I only run Ubuntu myself.
Have you had a go at restricting parallel builds?
It's not related to memory usage is it?
How very odd. No I don't really know I am afraid. I only run Ubuntu myself.
Have you had a go at restricting parallel builds?
No, because the mono recipe runs make
directly, restricting parallel builds to -j1
out of the box.
The recipe should use oe_runmake
to do parallel build. But using it doesn't influence anything regarding the observed crashes, only the speed to reproduce them.
It's not related to memory usage is it?
It doesn't seem so.
Most odd. Has anybody upstream had anything to say about this maybe?
This may not be a good idea but potentially we could try to replicate this by making a docker CI build container using Fedora rather than Ubuntu?
This is indeed strange.
The crash dump (i.e. the bytes as shown in the Memory around native instruction pointer
message is identical across different DLL builds but it's sporadic in the sense that sometimes different DLLs show the issue.
And it WAS working previously. So it's an upgrade that causes this.
(after a lot of trial and error today)
TADA: 6.2.12 kernel allows building mono-native, 6.2.13 and 6.2.14 started crashing the Mono build.
What's left is to
Sadly, 6.3.1 also crashes the build.
Reported the issue in the Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2196250
Very very odd indeed eh
FWIW, the cross-compiled Mono seems to work with kernel 6.2.14.
mono cert-sync.exe
works
Not sure what causes this. Kernel 6.2.x? GLIBC? GCC 13?
The same crash occurs a couple of times for different DLLs until the build finally stops.
FWIW, I looked at the Fedora SRPM / spec for possible fixes.
-O1
instead of-O2
didn't workI am out of ideas at the moment.
@ajlennon Any idea?