>> Ktrace it
> That, way, it proceeds past the error.
!! That's a very strong clue. I'm not sure what it's a clue to, but
it's got to mean _something_; ktracing, as I understand it, should be
invisible to the traced program, except for a slight performance hit.
/~\ The ASCII
> Ktrace it
That, way, it proceeds past the error.
I can then interrupt it and proceed with a normal make build.
That core dumps again (later); ktrace-d, it proceeds past the error again.
Interrupt, proceed normal. core dumps.
Finally, I get a core dump with the ktrace-d run, but no sensible backtr
On Thu, Jun 30, 2022 at 07:29:18PM +0200, Edgar Fuß wrote:
> #8 0x77a601860ac0 in err () from /usr/lib/libc.so.12
> #9 0x77a60280c47b in pthread__init () from /usr/lib/libpthread.so.1
Ktrace it - there are 3 err() calls in pthread__init(),
one after sysctl hw.ncpu failed, one if _lwp_unp
In order to be able to build packages for -6 on a -8 machine, I set up a
subdirectroy in /var/chroot containing a tar-ed copy of a real -6 machine.
I then chroot into there with kver -r 6.1_STABLE /bin/sh.
I tried to build icinga2, but I cmake core dumps with this backtrace:
#0 0x77a6028076
