On 5/9/19 2:40 AM, Ken Moffat wrote:
On Wed, May 08, 2019 at 09:47:40PM -0400, Baho utot wrote:
More info on segfaults:
built perl on pclinuxos saw no segfaults during the build
Opened the syslog and boom here it is:
May 8 21:41:16 desktop kernel: perl[16059]: segfault at 7ffeba075ff8 ip
00007ff75122dd85 sp 00007ffeba076000 error 6 in
Storable.so[7ff751223000+14000]
May 8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 ip
00007fb95267653c sp 00007ffc0742c000 error 6 in
Storable.so[7fb95266b000+14000]
May 8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 ip
00007f09a4b851fc sp 00007ffd42293000 error 6 in
Storable.so[7f09a4b7b000+14000]
May 8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 ip
00007f09a780fa72 sp 00007fff15dbc000 error 6 in
libperl.so[7f09a7761000+15d000]
May 8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 ip
00007fd4ad18d1f2 sp 00007ffde0594fe0 error 6 in
Storable.so[7fd4ad183000+14000]
May 8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 ip
00007f5b83ac1ebd sp 00007ffed745ffc0 error 6 in
ld-2.29.so[7f5b83ab9000+1e000]
May 8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 ip
00007f9972d4f3cb sp 00007fffb59a8fd0 error 6 in
Storable.so[7f9972d43000+14000]
May 8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 ip
00007f0f722d11fe sp 00007fffa7a92ff0 error 6 in
libc-2.29.so[7f0f7226d000+154000]
May 8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 ip
00007f1b3a047e4b sp 00007ffc911c7fc0 error 6 in
libc-2.29.so[7f1b39fe5000+154000]
May 8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 ip
00007fcd75ed7e4b sp 00007ffe790b9ff0 error 6 in
libc-2.29.so[7fcd75e75000+154000]
It looked like it built correctly from watching the build but if you don't
look in the syslog you will not know that they occured
Can some one have a look in their syslog after they just built perl to see
if it was clean?
I did the following:
tail -f /var/log/syslog
Yes it is syslog on pclinuxos and not sys.log
As it happens, I'm stuck in building current LFS-svn (failed sanity
check after installing gcc in chroot). So, I've still got the
syslog from building perl in chapter 5, and yes, loads of segfaults
(but not as many as from the gcc tests).
So, presumably perl-5.26 is constructed differently from 5.26. Maybe
a side-effect of the work the perl maintainers put into fixing CVEs
last year.
And the reason why you saw these on the screen in LFS, but not in
pclinuxos is probably a matter of kernel/bootscript configuration:
For the LFS bootscripts, see section 7.6.5 'Configuring the Linux
Console' ('LOGLEVEL') : I'm using "4"
or for the kernel itself (this is from 5.0)
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
Normally, if I look at the syslog after a build, it is at the end
and by that stage anything from chapter 5 is by definition not
interesting.
Summary: these segfaults fro mperl, and not just from running the
tests, turn out to be normal and can be configured out of the terms.
So, I was wrong in saying that they only came from failign tests.
Well, not the first time I've been wrong, I'm sure it will happen
again.
Hope the rest of it goes ok, and then when you hit problems in BLFS
please ask - but remember that not everyone has the same interests,
and very few people build exactly the same desktop packages.
I have also tried perl-5.28.2 same issue.
BLFS is a bit down the road, want to get LFS-8.4 working oon a
raspberry pi first
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
