Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 00D4FE00DFD; Thu, 15 Aug 2019 21:40:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [82.221.130.149 listed in list.dnswl.org] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received: from smtp.vivaldi.net (smtp.vivaldi.net [82.221.130.149]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 52A16E00D35 for ; Thu, 15 Aug 2019 21:40:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp.vivaldi.net (Postfix) with ESMTP id 135EC3FAF0; Fri, 16 Aug 2019 04:40:51 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 smtp.vivaldi.net 135EC3FAF0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=mail; t=1565930451; bh=m/WD8jXC/KgskexMWG4rIUgsK9Q/rkSBlU92pRWeh4U=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=cKyBtqX+6NC2gfmeCQz4jNoy6baHL/taJgXejKOY7MUWXw1QchkBUbe8TZct9pVd0 c+eNG3wQLRZdMWd4cFwxycX6wkyIV56OlM5gs2uY9A7XwixOTos/fIvXtHDYWWxkGy GpopcViCfTjwoLfmsSuoSlz8samojE6nj7+1G+c/iSaAHFJnuFWZgKhpXpBk1vx1Xi o1yXXoaLvlJij9LFVRatuEqeDIdcIEFV4dgvPpC1UmuqRfxHpj9VAHGB7fL40Ukp0Y 8GWgbgV2EG7atWxBHxufAVFCunguMoEjZwyyrx6kAsttqUWxKastvNEwJkyw8tE5O4 RCCt5wJrXyC7g== X-Virus-Scanned: Debian amavisd-new at smtp.vivaldi.net Received: from smtp.vivaldi.net ([127.0.0.1]) by localhost (mxo-new.viv.ext [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gg46LCDnNd0y; Fri, 16 Aug 2019 04:40:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.10.3 smtp.vivaldi.net 20C143F9F2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vivaldi.net; s=mail; t=1565930449; bh=m/WD8jXC/KgskexMWG4rIUgsK9Q/rkSBlU92pRWeh4U=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=W08hd8WDANnvJrB9is4+TQIrdpinel8yQRoXllWAdRi1sgoTSe0VUhMUJNbiCaR3R rCRpKrQxjIH6muhdUCHeXzCW4KP/zGzgFO6neOU0N5fmR+VMdO1MDkBUmxOApB/QpA wW5fqGh/zZiCujVrK/voj1TPX27P2QMsF4l4fJl4tkqAbe2dUYW96nIUT0RjaFtHtT 1LBfxVJmZSHmOeZRA/mr7DytXae6jMZTC3a5OtP7KN8mqgIkKVWZ5a/9iZOHGZgD1K GyRXbhlvOCRjTXPbvrbIQRmwIWOzBKkew3nFKBjezRIxqpqGh/4eJh7Y1YICUcmejj UdcR4NZ9Dx2cA== Date: Fri, 16 Aug 2019 10:10:46 +0530 From: jaymin.dabhi@vivaldi.net To: Randy MacLeod In-Reply-To: <1997fc5b-2e25-c56a-c423-dd2c62404971@windriver.com> References: <279ea8172bf6d37d284e8d5cb4efb077@vivaldi.net> <1997fc5b-2e25-c56a-c423-dd2c62404971@windriver.com> Message-ID: X-Sender: jaymin.dabhi@vivaldi.net User-Agent: Roundcube Webmail/1.3.9 Cc: yocto@yoctoproject.org Subject: Re: Segmentation fault | bitbake machine-image.bb | core dumped X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2019 04:40:55 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Randy, Thanks for your information regarding Yocto Jethro branch. Yes, this core dumped issue is reproducible. When I add python3-pip package in local.conf file and build complete image, this core dumped is happening. Randy, it would be much helpful if you explain me how to adjust core file limits using ulimit, and how get the backtrace? I have added python3-pip package in local.conf file, this is the one change only I did in local.conf. Yes, I am able to generate the image successfully after reverting this one change. Please let me know if more information require. On 15-08-2019 07:30 AM, Randy MacLeod wrote: > On 8/12/19 10:42 AM, jaymin.dabhi@vivaldi.net wrote: >> Hello All, >> >> Facing segmentation fault (core dumped) while doing bitbake. >> I am using Yocto Jethro branch. > > Jethro isn't officially supported by the Yocto Project. > The support cycle is ~ 1 year. > > https://wiki.yoctoproject.org/wiki/Releases > > Can you reproduce the issue on master or a newer supported branch? > If so you could file a bug in: > https://wiki.yoctoproject.org/wiki/Releases > > Also, see below for some tips. > >> >> When I added python3-pip recipe (in local.conf) and started building >> image, segmentation fault occurred. >> Although, I am able to bitbake python3-pip individually (i.e. bitbake >> python3-pip). >> As per log my assumption is, core dumped is occurring at make_ext4fs >> execution. >> >> Following are the error logs: >> >> ERROR: Function failed: do_makesystem (log file is located at >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059) >> ERROR: Logfile of failure stored in: >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059 >> Log data follows: >> | DEBUG: Executing shell function do_makesystem >> | >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/run.do_makesystem.15059: >> line 105: 15073 Segmentation fault      (core dumped) make_ext4fs -J >> -b 1024 -s -a / -S > > Odd, I've never see that happen before. > Is it reproducible? > > Can you adjust the core file limits using 'ulimit', > generate a core file and get a backtrace? > >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs/etc/selinux/mls/contexts/files/file_contexts >> -l 768000000 >> poky/build/tmp-glibc/deploy/images/apq8053-perf/apq8053-sysfs.ext4 >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs >> | WARNING: >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/run.do_makesystem.15059:1 >> exit 139 from >> |   make_ext4fs -J -b 1024 -s -a / -S >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs/etc/selinux/mls/contexts/files/file_contexts >> -l 768000000 >> poky/build/tmp-glibc/deploy/images/apq8053-perf/apq8053-sysfs.ext4 >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs >> | ERROR: Function failed: do_makesystem (log file is located at >> poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059) >> ERROR: Task 11 ( >> poky/meta-qti-bsp/recipes-products/images/machine-image.bb, >> do_makesystem) failed with exit code '1' >> >> >> Whether python3-pip recipe is creating an issue or something else? >> (attached the python3-pip recipe file) > > What did you change in your conf/local.conf file? > If you revert that change, then you are able to generate the image > again? > > ../Randy > >> Please let me know. >> Any suggestions are welcome. >> >> Regards, >> Jaymin >> > > > -- > # Randy MacLeod > # Wind River Linux