> No, this is just too early in the init sequence.
> It shouldn't be using err()...
Then someone(TM) should fix that?
Shall I file a PR?
On Sat, Jul 02, 2022 at 12:02:49AM +0700, Robert Elz wrote:
> Date:Fri, 1 Jul 2022 17:46:06 +0200
> From:Edgar =?iso-8859-1?B?RnXf?=
> Message-ID:
>
> | What I don't understand is why it dumps core while reporting an error.
>
> Perhaps NetBSD 6 required an
EF> What I don't understand is why it dumps core while reporting an error.
KRE> Perhaps NetBSD 6 required an explicit setprogname() which is no longer
KRE> required?
But that's a matter of the C library, no?
Date:Fri, 1 Jul 2022 17:46:06 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID:
| What I don't understand is why it dumps core while reporting an error.
Perhaps NetBSD 6 required an explicit setprogname() which is no longer
required ? [I no longer remember].
> you could test with paxctl on the cmake file
With paxctl +m /usr/pkg/bin/cmake (inside the chroot, of course),
it now core dumps even earlier in the build, with
#0 0x0079d33c in
cmsys::SystemTools::FilesDiffer(std::__cxx11::basic_string, std::allocator > const&,
On Fri, Jul 01, 2022 at 02:20:02PM +0200, Edgar Fuß wrote:
> > Ktrace it
> As mentioned, that doesn't work (well, it works, which is the problem).
>
> > there are 3 err() calls in pthread__init()
>
> Starting with
> #8 0x71b551460ac0 in err () from /usr/lib/libc.so.12
> #9
> Ktrace it
As mentioned, that doesn't work (well, it works, which is the problem).
> there are 3 err() calls in pthread__init()
Starting with
#8 0x71b551460ac0 in err () from /usr/lib/libc.so.12
#9 0x71b55240c47b in pthread__init () from /usr/lib/libpthread.so.1
I
> but it's got to mean _something_
Timing?
>> 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
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
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
12 matches
Mail list logo
