Date: Sun, 3 May 2020 16:01:51 +0100 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-current@freebsd.org Subject: Re: lock order reversal and poudriere Message-ID: <b7c10154-9a3e-baf6-7ed5-007f01b701d7@gjunka.com> In-Reply-To: <d47b5c72-4541-4f53-c8dc-9763175e1ed8@daemonic.se> References: <68514e96-f1a5-0c8d-998f-bf81034ed61d@gjunka.com> <20200502095404.GN39563@home.opsec.eu> <b2a13239-e65e-5385-8b87-3ff0942d3d8a@gjunka.com> <20200502183634.GA90255@fc.opsec.eu> <d47b5c72-4541-4f53-c8dc-9763175e1ed8@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/05/2020 15:00, Niclas Zeising wrote: > On 2020-05-02 20:36, Kurt Jaeger wrote: >> >> I don't know, either 8-} bz@ is in Cc:, so he'll probably know what >> to do. >> >>> How do I know if I have got a backtrace? >>> >>> Are those errors: >>> >>> pid 43297 (conftest), jid 5, uid 0: exited on signal 11 >>> >>> related or it's a different issue? >> >> I think that's a different issue. >> > > conftest is when configure scripts do things. Configure works a lot > by compiling (and sometimes running) small snippets of code to figure > out what's going on. Sometimes those snippets core dump. It's all > normal. > Good to know. It's mostly conftest but sometimes others too: pid 37407 (cc), jid 9, uid 0: exited on signal 6 pid 95358 (conftest), jid 3, uid 0: exited on signal 11 pid 70242 (conftest), jid 9, uid 0: exited on signal 11 pid 27480 (ngc27183), jid 3, uid 0: exited on signal 11 Regards --GrzegorzJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b7c10154-9a3e-baf6-7ed5-007f01b701d7>