Date: Thu, 21 May 2020 10:23:05 +0300 From: Yuri Pankov <ypankov@fastmail.com> To: Grzegorz Junka <list1@gjunka.com>, freebsd-ports@freebsd.org Subject: Re: poudriere segmentation fault on 13-CURRENT Message-ID: <096c8777-2a0f-85b9-812d-fa2f8574df5a@fastmail.com> In-Reply-To: <899a6cae-6c3e-1b91-6560-8823ba654ff4@gjunka.com> References: <2b044d26-5ba8-ff6b-bf00-d1d0b18b4fb2@gjunka.com> <af196323-83bc-415a-2af7-401bd25f0439@fastmail.com> <899a6cae-6c3e-1b91-6560-8823ba654ff4@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Grzegorz Junka wrote: > > On 20/05/2020 19:33, Yuri Pankov wrote: >> Grzegorz Junka wrote: >>> When configuring ports with this option: >>> >>> poudriere options -j 13 -p gui -z v8 lang/v8 >>> >>> for every port the configuration ends with "Segmentation fault". For >>> example, with that command the first port that shows up is >>> "python27-2.7.18". After the ncurses dialog is shown I click OK which >>> supposed to save the option. But instead, I see "Segmentation fault" >>> and nothing is written to >>> /usr/local/etc/poudriere.d/13-gui-v8-options/lang_python27/ >>> >>> This only happens when I use kernel 13-CURRENT and "Segmentation >>> fault" would happen regardless if used -j 13 or -j 12 or -j 12.1 >>> (STABLE and 12.1 jails respectively). Otherwise compiling with >>> poudriere on kernel 13 works fine, it's just the options that don't >>> work. >>> >>> I have to boot kernel 12, configure options, then boot kernel 13 to >>> compile. >>> >>> What might be the issue? >> >> Which program is misbehaving, is it dialog4ports? Do you have the core >> and can provide the backtrace? > > That's what I would like to find out. No core is dumped in the local > folder. Not sure where it would be dumped instead? If at all? > > The segmentation fault happens after the options have been selected. I > think it's at the moment when they should have been written to disk. You can check dmesg for that information, e.g.: pid 41216 (sleep), jid 0, uid 1001: exited on signal 11 pid 43373 (bad), jid 0, uid 1001: exited on signal 11 (core dumped) Note that the former doesn't say the "core dumped" as I just sent SIGSEGV to it using `pkill`, the latter is small test case dereferencing null pointer, and has its core written to the working directory. Also, is it reproducible without using poudriere? Is it running 12.x binaries with 13-CURRENT kernel? If yes, what are the revisions for both?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?096c8777-2a0f-85b9-812d-fa2f8574df5a>