[yocto] Segmentation fault | bitbake machine-image.bb | core dumped

[jaymin.dabhi at vivaldi.net]

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 at 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