Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-10 Thread Eric Junkermann 
On Thu, 9 May 2019 10:35:02 -0500, Bruce Dubbs  wrote:
8>< 
> Using
> 
> ulimit -s unlimited
> 
> before 'make' allows the build to complete without any segfaults.

But that's not a good idea, because

 the stack size at build time might be different at run time, eg. the
 stack size may have been modified with ulimit(1). If it's larger at run
 time Storable may fail the freeze() or thaw() unnecessarily. If it's
 larger at build time Storable may segmentation fault when processing
 a deep structure at run time.

(a quote from the Storable 3.15 doc at
https://metacpan.org/pod/Storable)

i.e. the build should be done at whatever the ulimit is for a _normal
user_.

8>< 
> 
> My conclusion is that the segfaults are caused intentionally when trying 
> to determine the recursion limit and we do not need to do anything.

Agreed. Perl 5.28.1 which is in LFS 8.4 comes with Storable 3.08.
Storable 3.15 (current in CPAN) does not do the recursion level tests
any more, so with any luck LFS 8.5 will not have the segfaults (Perl
5.29, still Devel, has Storable 3.15).

Eric
-- 
ms fnd in a lbry
-- 
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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Douglas R. Reno 


On 5/9/19 8:09 AM, Baho utot wrote:


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

7ff75122dd85 sp 7ffeba076000 error 6 in
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 
7ffc0742bff8 ip

7fb95267653c sp 7ffc0742c000 error 6 in
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 
7ffd42292ff8 ip

7f09a4b851fc sp 7ffd42293000 error 6 in
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 
7fff15dbbff8 ip

7f09a780fa72 sp 7fff15dbc000 error 6 in
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 
7ffde0594ff8 ip

7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 
7ffed745ffc0 ip

7f5b83ac1ebd sp 7ffed745ffc0 error 6 in
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 
7fffb59a8fd8 ip

7f9972d4f3cb sp 7fffb59a8fd0 error 6 in
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 
7fffa7a92fe8 ip

7f0f722d11fe sp 7fffa7a92ff0 error 6 in
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 
7ffc911c7fc8 ip

7f1b3a047e4b sp 7ffc911c7fc0 error 6 in
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 
7ffe790b9ff8 ip

7fcd75ed7e4b sp 7ffe790b9ff0 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




Here's some advice on that from my experiments a while back with it:

GCC needs a patch (applies cleanly in Pass 1, 2, and CH6):

https://intestinate.com/pilfs/patches/gcc-5.3.0-rpi3-cpu-default.patch 
(THIS IS FOR Pi 3s)


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Eric Junkermann 
On Thu, 9 May 2019 08:58:35 -0400, Baho utot  wrote:
8>< 
>  From what I can tell it comes from Storable.so when it is built, don't 
> know what is causing it

I have not long finished building LFS 8.4 using LFS 8.0 as the host
(+stuff from BLFS). This is my only system and it is doing everything
I need it to. I had no problems in the build that weren't my own fault.
Most of the BLFS things were built on the running 8.4 (NOT in the chroot)

I have had no reason to rebuild perl, but after watching this
conversation for a while I have tried it out, and yes, I get segfaults.
Some of the messages (in sys.log) even quote "Storable.so", so you are
probably right about that. Given that, it is easier to try building just
Storable (you have to do it after running Configure and make for the
full build):

 cd dist/Storable
 perl Makefile.PL
 make

The segfaults show up, and the output of the make includes

 Storable: determining recursion limit: 65000 too big, try less 32550 ...
 Storable: determining recursion limit: 32550 too big, try less 16325 ...
 Storable: determining recursion limit: 16325 passed, try more 24437 ...
 Storable: determining recursion limit: 24437 too big, try less 20381 ...

and more of the same - each "too big" is a segfault (there seem to be
a couple extra which I haven't tracked down) and THEY ARE DELIBERATE,
the limits determined by this process are used to stop Storable from
segfaulting at runtime. The design (and purpose) of Storable mean that
it will sometimes need deep recursion.

Obviously the number of segfaults you get will depend on memory, the
kernel and I don't know how many other things, but there is no need to
worry about them, move on.

Eric
-- 
ms fnd in a lbry
-- 
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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Pierre Labastie 
On 09/05/2019 17:35, Bruce Dubbs wrote:
> On 5/9/19 3:55 AM, Michael Shell wrote:
>> On Tue, 7 May 2019 17:50:28 -0400
>> baho-u...@columbus.rr.com wrote:
>>
>>> May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip
>>> 0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]
>>
>>
>> Perhaps this is the same issue discussed here:
>>
>> https://www.perlmonks.org/?node_id=1002749
>>
>> about a possible memory limit issue.
>>
>> Does using ulimit to increase the data segment size also fix
>> the problem for your case as well?
>>
>> ulimit -n 1024 -u 35 -m 20 -d unlimited -s 8192 -c 20 -v 2000
> 
> If I use that line before 'make -j4 > m.log' I get
> 
> ./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
> ./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
> ./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
> ./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
> ./make-perl-5.28.2-Chap5.sh: fork: Resource temporarily unavailable
> 
> and nothing gets built.  That appears to be due to the -v (virtual memory) 
> limit.
> 
> Fortunately, the build does not take very long and I can test a lot of
> variations relatively quickly. Using
> 
> ulimit -s unlimited
> 
> before 'make' allows the build to complete without any segfaults.
> 
> Also, watching sys.log while building says the segfaults currently happening
> are at the end of the build.  Looking at the stdout build log I see:
> 
> Storable: determining recursion limit: 65000 passed, try more 65000 ...
> MAX_DEPTH = 65000
> Storable: determining recursion limit: 32500 too big, try less 16275 ...
> Storable: determining recursion limit: 16275 too big, try less 8163 ...
> Storable: determining recursion limit: 8163 too big, try less 4107 ...
> Storable: determining recursion limit: 4107 too big, try less 2079 ...
> Storable: determining recursion limit: 2079 too big, try less 1065 ...
> Storable: determining recursion limit: 1065 too big, try less 558 ...
> Storable: determining recursion limit: 558 too big, try less 304 ...
> Storable: determining recursion limit: 304 passed, try more 431 ...
> Storable: determining recursion limit: 431 passed, try more 494 ...
> Storable: determining recursion limit: 494 passed, try more 526 ...
> Storable: determining recursion limit: 526 too big, try less 510 ...
> Storable: determining recursion limit: 510 passed, try more 518 ...
> Storable: determining recursion limit: 518 too big, try less 514 ...
> Storable: determining recursion limit: 514 too big, try less 512 ...
> Storable: determining recursion limit: 512 passed, try more 513 ...
> Storable: determining recursion limit: 513 passed, try more 513 ...
> MAX_DEPTH_HASH = 513
> 
> but without the ulimit line I get
> 
> Storable: determining recursion limit: 65000 too big, try less 32550 ...
> Storable: determining recursion limit: 32550 too big, try less 16325 ...
> Storable: determining recursion limit: 16325 passed, try more 24437 ...
> Storable: determining recursion limit: 24437 passed, try more 28493 ...
> Storable: determining recursion limit: 28493 too big, try less 26465 ...
> Storable: determining recursion limit: 26465 too big, try less 25451 ...
> Storable: determining recursion limit: 25451 too big, try less 24944 ...
> Storable: determining recursion limit: 24944 too big, try less 24691 ...
> Storable: determining recursion limit: 24691 passed, try more 24817 ...
> Storable: determining recursion limit: 24817 passed, try more 24880 ...
> Storable: determining recursion limit: 24880 passed, try more 24912 ...
> Storable: determining recursion limit: 24912 passed, try more 24928 ...
> Storable: determining recursion limit: 24928 passed, try more 24936 ...
> Storable: determining recursion limit: 24936 passed, try more 24940 ...
> Storable: determining recursion limit: 24940 too big, try less 24938 ...
> Storable: determining recursion limit: 24938 too big, try less 24937 ...
> Storable: determining recursion limit: 24937 too big, try less 24937 ...
> MAX_DEPTH = 24936
> Storable: determining recursion limit: 12468 too big, try less 6259 ...
> Storable: determining recursion limit: 6259 too big, try less 3155 ...
> Storable: determining recursion limit: 3155 too big, try less 1603 ...
> Storable: determining recursion limit: 1603 too big, try less 827 ...
> Storable: determining recursion limit: 827 too big, try less 439 ...
> Storable: determining recursion limit: 439 passed, try more 633 ...
> Storable: determining recursion limit: 633 too big, try less 536 ...
> Storable: determining recursion limit: 536 too big, try less 488 ...
> Storable: determining recursion limit: 488 passed, try more 512 ...
> Storable: determining recursion limit: 512 passed, try more 524 ...
> Storable: determining recursion limit: 524 too big, try less 518 ...
> Storable: determining recursion limit: 518 too big, try less 515 ...
> Storable: determining rec

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Thomas Trepl 
Am Dienstag, den 07.05.2019, 08:24 -0400 schrieb baho-
u...@columbus.rr.com:
> Building perl ( both chapter 5 and 6 ) under the host system (pclinuxos) 
> works fine.
> 
> The issue is when I use the newly built LFS-8.4 to build its self ie as 
> the host system.
> 
> The perl build for both chapter 5 and chapter 6 produces some segfaults 
> outputs to stderr.
> 
> The build always completes and I when boot to this new build (lfs as the 
> host) and it works.
> 
> The last LFS ( version 8.2 ) I built does not do this when using it to 
> "rebuild its self".
> 
> Has anyone seen this?
> 
Yes. I quickly run a test build on a LFS-8.4 producing a LFS-SVN
system using a ssh session and in parallel watching the console of
that VM via RDP. On console i got several segfault messages presented:


7ffeee618ff0 error 6 in Storable.so[7f55fe945000+14000]
[354156.417589] Code: 41 55 49 89 fd 41 54 49 89 d4 55 48 89 f5 53 48
83 ec 20 4c 8b 76 08 64 48 8b 04 25 28 00 00 00 48 89 44 24 18 31 c0
4c 89 f6  af 32 ff ff 48 85 c0 0f 84 f6 01 00 00 49 8d 95 50 01 00
00 49
[354156.507682] perl[2912]: segfault at 7fff26c7bff8 ip
7f00dc2ad476 sp 7fff26c7c000 error 6 in
Storable.so[7f00dc29f000+14000]
[354156.508061] Code: fc ff ff e8 3c 1d ff ff 41 c7 47 78 01 00 00 00
48 8d 3d 4d 66 00 00 31 c0 e8 26 1f ff ff 66 0f 1f 44 00 00 41 57 41
56 41 55 <41> 54 55 48 89 fd 53 48 89 f3 48 83 ec 18 44 8b 6a 0c 4c 8b
62 10
[354156.530198] perl[2914]: segfault at 7ffc84637ff8 ip
7fa2130b6c37 sp 7ffc84638000 error 6 in
libperl.so[7fa212ff3000+16]
[354156.531220] Code: 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41
5f c3 e8 9c d2 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 d0
48 89 fd <53> 48 89 d3 48 c1 e8 0a 48 c1 eb 03 48 31 c3 48 89 d0 48 c1
e8 14
[354156.582947] perl[2918]: segfault at 7ffcdd9e9ff8 ip
7f153acfdc37 sp 7ffcdd9ea000 error 6 in
libperl.so[7f153ac3a000+16]
[354156.583340] Code: 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41
5f c3 e8 9c d2 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 d0
48 89 fd <53> 48 89 d3 48 c1 e8 0a 48 c1 eb 03 48 31 c3 48 89 d0 48 c1
e8 14
[354156.659382] perl[2936]: segfault at 7ffe8b3f3ff8 ip
7feb5ff0af4e sp 7ffe8b3f3ff0 error 6 in
libperl.so[7feb5fe59000+16]
[354156.659743] Code: f5 ff 48 8b 44 24 08 49 8d 04 c7 e9 96 fd ff ff
e8 67 06 f5 ff 0f 1f 80 00 00 00 00 41 54 49 89 fc 55 48 89 f5 53 48
83 ec 10 <48> 89 54 24 08 f6 46 0e 80 0f 85 93 00 00 00 48 8b 45 00 48
8b 74


So it looks like it has been described somewhere in the thread. I
tried to catch the moment when the messages popped up on the console
to stop the pager showing me the log file (stopping "less +F perl.log"
by ^C). The last entries in the log looked like


chmod 755 ../../lib/auto/Math/BigInt/FastCalc/FastCalc.so
make[1]: Leaving directory '/autolfs/sources/perl-5.28.2/cpan/Math-
BigInt-FastCa
lc'
probe for max. stack sizes...
parallel build race - wait for linker ...
Storable: determining recursion limit: 65000 too big, try less 32550
...
Storable: determining recursion limit: 32550 too big, try less 16325
...
Storable: determining recursion limit: 16325 passed, try more 24437
...
Storable: determining recursion limit: 24437 too big, try less 20381
...
Storable: determining recursion limit: 20381 passed, try more 22409
...
Storable: determining recursion limit: 22409 passed, try more 23423
...
Storable: determining recursion limit: 23423 too big, try less 22916
...
Storable: determining recursion limit: 22916 too big, try less 22663
...
Storable: determining recursion limit: 22663 passed, try more 22789
...
rm -f ../../lib/auto/XS/APItest/APItest.so
cc  -shared -O2 -L/usr/local/lib -fstack-protector-strong  APItest.o
XSUB-undef-XS_VERSION.o XSUB-redefined-macros.o core.o exception.o
notcore.o  -o ../../lib/auto/XS/APItest/APItest.so  \
  \
  
Storable: determining recursion limit: 22789 too big, try less 22726
...
chmod 755 ../../lib/auto/XS/APItest/APItest.so
make[1]: Leaving directory '/autolfs/sources/perl-5.28.2/ext/XS-
APItest'
Storable: determining recursion limit: 22726 passed, try more 22757
...
Storable: determining recursion limit: 22757 passed, try more 22773
...
Storable: determining recursion limit: 22773 too big, try less 22765
...
Storable: determining recursion limit: 22765 passed, try more 22769
...
Storable: determining recursion limit: 22769 passed, try more 22771
...
Storable: determining recursion limit: 22771 passed, try more 22772
...
Storable: determining recursion limit: 22772 passed, try more 22772
...
MAX_DEPTH = 22772
Storable: determining recursion limit: 11386 too big, try less 5718
...
Storable: determining recursion limit: 5718 too big, try less 2884 ...
Storable: determining recursion limit: 2884 too big, try less 1467 ...
Storable: determining recursion limit: 1467 too big, try less 759 ...
Storable: determining recursion limit: 759 too big, try less 405 ...
Storable: determining recursion limit: 405 passed, try more 582 ...
Storable: determ

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Bruce Dubbs 

On 5/9/19 3:55 AM, Michael Shell wrote:

On Tue, 7 May 2019 17:50:28 -0400
baho-u...@columbus.rr.com wrote:


May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip
0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]



Perhaps this is the same issue discussed here:

https://www.perlmonks.org/?node_id=1002749

about a possible memory limit issue.

Does using ulimit to increase the data segment size also fix
the problem for your case as well?

ulimit -n 1024 -u 35 -m 20 -d unlimited -s 8192 -c 20 -v 2000


If I use that line before 'make -j4 > m.log' I get

./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
./make-perl-5.28.2-Chap5.sh: fork: retry: Resource temporarily unavailable
./make-perl-5.28.2-Chap5.sh: fork: Resource temporarily unavailable

and nothing gets built.  That appears to be due to the -v (virtual 
memory) limit.


Fortunately, the build does not take very long and I can test a lot of 
variations relatively quickly. Using


ulimit -s unlimited

before 'make' allows the build to complete without any segfaults.

Also, watching sys.log while building says the segfaults currently 
happening are at the end of the build.  Looking at the stdout build log 
I see:


Storable: determining recursion limit: 65000 passed, try more 65000 ...
MAX_DEPTH = 65000
Storable: determining recursion limit: 32500 too big, try less 16275 ...
Storable: determining recursion limit: 16275 too big, try less 8163 ...
Storable: determining recursion limit: 8163 too big, try less 4107 ...
Storable: determining recursion limit: 4107 too big, try less 2079 ...
Storable: determining recursion limit: 2079 too big, try less 1065 ...
Storable: determining recursion limit: 1065 too big, try less 558 ...
Storable: determining recursion limit: 558 too big, try less 304 ...
Storable: determining recursion limit: 304 passed, try more 431 ...
Storable: determining recursion limit: 431 passed, try more 494 ...
Storable: determining recursion limit: 494 passed, try more 526 ...
Storable: determining recursion limit: 526 too big, try less 510 ...
Storable: determining recursion limit: 510 passed, try more 518 ...
Storable: determining recursion limit: 518 too big, try less 514 ...
Storable: determining recursion limit: 514 too big, try less 512 ...
Storable: determining recursion limit: 512 passed, try more 513 ...
Storable: determining recursion limit: 513 passed, try more 513 ...
MAX_DEPTH_HASH = 513

but without the ulimit line I get

Storable: determining recursion limit: 65000 too big, try less 32550 ...
Storable: determining recursion limit: 32550 too big, try less 16325 ...
Storable: determining recursion limit: 16325 passed, try more 24437 ...
Storable: determining recursion limit: 24437 passed, try more 28493 ...
Storable: determining recursion limit: 28493 too big, try less 26465 ...
Storable: determining recursion limit: 26465 too big, try less 25451 ...
Storable: determining recursion limit: 25451 too big, try less 24944 ...
Storable: determining recursion limit: 24944 too big, try less 24691 ...
Storable: determining recursion limit: 24691 passed, try more 24817 ...
Storable: determining recursion limit: 24817 passed, try more 24880 ...
Storable: determining recursion limit: 24880 passed, try more 24912 ...
Storable: determining recursion limit: 24912 passed, try more 24928 ...
Storable: determining recursion limit: 24928 passed, try more 24936 ...
Storable: determining recursion limit: 24936 passed, try more 24940 ...
Storable: determining recursion limit: 24940 too big, try less 24938 ...
Storable: determining recursion limit: 24938 too big, try less 24937 ...
Storable: determining recursion limit: 24937 too big, try less 24937 ...
MAX_DEPTH = 24936
Storable: determining recursion limit: 12468 too big, try less 6259 ...
Storable: determining recursion limit: 6259 too big, try less 3155 ...
Storable: determining recursion limit: 3155 too big, try less 1603 ...
Storable: determining recursion limit: 1603 too big, try less 827 ...
Storable: determining recursion limit: 827 too big, try less 439 ...
Storable: determining recursion limit: 439 passed, try more 633 ...
Storable: determining recursion limit: 633 too big, try less 536 ...
Storable: determining recursion limit: 536 too big, try less 488 ...
Storable: determining recursion limit: 488 passed, try more 512 ...
Storable: determining recursion limit: 512 passed, try more 524 ...
Storable: determining recursion limit: 524 too big, try less 518 ...
Storable: determining recursion limit: 518 too big, try less 515 ...
Storable: determining recursion limit: 515 too big, try less 514 ...
Storable: determining recursion limit: 514 too big, try less 513 ...
Storable: determining recursion limit: 513 passed, try more 513 ...
MAX_DEPTH_HASH = 513

My conclusion is that th

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Baho utot 


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
7ff75122dd85 sp 7ffeba076000 error 6 in
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 ip
7fb95267653c sp 7ffc0742c000 error 6 in
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 ip
7f09a4b851fc sp 7ffd42293000 error 6 in
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 ip
7f09a780fa72 sp 7fff15dbc000 error 6 in
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 ip
7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 ip
7f5b83ac1ebd sp 7ffed745ffc0 error 6 in
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 ip
7f9972d4f3cb sp 7fffb59a8fd0 error 6 in
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 ip
7f0f722d11fe sp 7fffa7a92ff0 error 6 in
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 ip
7f1b3a047e4b sp 7ffc911c7fc0 error 6 in
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 ip
7fcd75ed7e4b sp 7ffe790b9ff0 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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Baho utot 


On 5/9/19 12:47 AM, Bruce Dubbs wrote:

On 5/8/19 8:47 PM, 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 7ff75122dd85 sp 7ffeba076000 error 6 in 
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 
ip 7fb95267653c sp 7ffc0742c000 error 6 in 
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 
ip 7f09a4b851fc sp 7ffd42293000 error 6 in 
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 
ip 7f09a780fa72 sp 7fff15dbc000 error 6 in 
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 
ip 7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in 
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 
ip 7f5b83ac1ebd sp 7ffed745ffc0 error 6 in 
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 
ip 7f9972d4f3cb sp 7fffb59a8fd0 error 6 in 
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 
ip 7f0f722d11fe sp 7fffa7a92ff0 error 6 in 
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 
ip 7f1b3a047e4b sp 7ffc911c7fc0 error 6 in 
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 
ip 7fcd75ed7e4b sp 7ffe790b9ff0 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


I did a test build and did get those segfaults in my log.  There were 
10 instances over about 0.3 seconds.


Mine look a little different.  The log entries are in pairs. For 
example (formatted):


May  8 15:43:37 frodo84 kernel: [4311687.668999] perl[23266]:
segfault at 7ffe87508ff8
ip 004e5012
sp 7ffe87509000 error 6 in perl[407000+22c000]

May  8 15:43:37 frodo84 kernel: [4311687.669009]
Code: 00 b8 04 69 64 00 48 0f 45 d0 89 ee bf 20 56 67 00 31 c0 e8 30
  63 09 00 ba 16 87 c9 00 eb eb 66 0f 1f 84 00 00 00 00 00 41 56
  <41> 55 41 54 49 89 f4 55 48 89 fd 53 48 83 ec 20 4c 8b 6f 08
  64 48

I did not do an install for this test.  It does not happen in the 
Configure command so something in one of the Makefiles is causing it, 
but I can't find a reference in the log.


  -- Bruce




From what I can tell it comes from Storable.so when it is built, don't 
know what is causing it


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Baho utot 


On 5/9/19 4:55 AM, Michael Shell wrote:

ulimit -n 1024 -u 35 -m 20 -d unlimited -s 8192 -c 20 -v 2000



Tried that and it did not work,  I think that fixed a different issue

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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Michael Shell 
On Tue, 7 May 2019 17:50:28 -0400
baho-u...@columbus.rr.com wrote:

> May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip 
> 0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]


Perhaps this is the same issue discussed here:

https://www.perlmonks.org/?node_id=1002749

about a possible memory limit issue.

Does using ulimit to increase the data segment size also fix
the problem for your case as well?

ulimit -n 1024 -u 35 -m 20 -d unlimited -s 8192 -c 20 -v 2000


  Cheers,

  Mike Shell
-- 
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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-09 Thread Ken Moffat 
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
> 7ff75122dd85 sp 7ffeba076000 error 6 in
> Storable.so[7ff751223000+14000]
> May  8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 ip
> 7fb95267653c sp 7ffc0742c000 error 6 in
> Storable.so[7fb95266b000+14000]
> May  8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 ip
> 7f09a4b851fc sp 7ffd42293000 error 6 in
> Storable.so[7f09a4b7b000+14000]
> May  8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 ip
> 7f09a780fa72 sp 7fff15dbc000 error 6 in
> libperl.so[7f09a7761000+15d000]
> May  8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 ip
> 7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in
> Storable.so[7fd4ad183000+14000]
> May  8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 ip
> 7f5b83ac1ebd sp 7ffed745ffc0 error 6 in
> ld-2.29.so[7f5b83ab9000+1e000]
> May  8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 ip
> 7f9972d4f3cb sp 7fffb59a8fd0 error 6 in
> Storable.so[7f9972d43000+14000]
> May  8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 ip
> 7f0f722d11fe sp 7fffa7a92ff0 error 6 in
> libc-2.29.so[7f0f7226d000+154000]
> May  8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 ip
> 7f1b3a047e4b sp 7ffc911c7fc0 error 6 in
> libc-2.29.so[7f1b39fe5000+154000]
> May  8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 ip
> 7fcd75ed7e4b sp 7ffe790b9ff0 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.

ĸen
-- 
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
 - wiki.lspace.org/mediawiki/Music_With_Rocks_In


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Bruce Dubbs 

On 5/8/19 8:47 PM, 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 
7ff75122dd85 sp 7ffeba076000 error 6 in 
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 ip 
7fb95267653c sp 7ffc0742c000 error 6 in 
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 ip 
7f09a4b851fc sp 7ffd42293000 error 6 in 
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 ip 
7f09a780fa72 sp 7fff15dbc000 error 6 in 
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 ip 
7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in 
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 ip 
7f5b83ac1ebd sp 7ffed745ffc0 error 6 in 
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 ip 
7f9972d4f3cb sp 7fffb59a8fd0 error 6 in 
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 ip 
7f0f722d11fe sp 7fffa7a92ff0 error 6 in 
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 ip 
7f1b3a047e4b sp 7ffc911c7fc0 error 6 in 
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 ip 
7fcd75ed7e4b sp 7ffe790b9ff0 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


I did a test build and did get those segfaults in my log.  There were 10 
instances over about 0.3 seconds.


Mine look a little different.  The log entries are in pairs. For example 
(formatted):


May  8 15:43:37 frodo84 kernel: [4311687.668999] perl[23266]:
segfault at 7ffe87508ff8
ip 004e5012
sp 7ffe87509000 error 6 in perl[407000+22c000]

May  8 15:43:37 frodo84 kernel: [4311687.669009]
Code: 00 b8 04 69 64 00 48 0f 45 d0 89 ee bf 20 56 67 00 31 c0 e8 30
  63 09 00 ba 16 87 c9 00 eb eb 66 0f 1f 84 00 00 00 00 00 41 56
  <41> 55 41 54 49 89 f4 55 48 89 fd 53 48 83 ec 20 4c 8b 6f 08
  64 48

I did not do an install for this test.  It does not happen in the 
Configure command so something in one of the Makefiles is causing it, 
but I can't find a reference in the log.


  -- Bruce


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Baho utot 

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 
7ff75122dd85 sp 7ffeba076000 error 6 in 
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 7ffc0742bff8 ip 
7fb95267653c sp 7ffc0742c000 error 6 in 
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 7ffd42292ff8 ip 
7f09a4b851fc sp 7ffd42293000 error 6 in 
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 7fff15dbbff8 ip 
7f09a780fa72 sp 7fff15dbc000 error 6 in 
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 7ffde0594ff8 ip 
7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in 
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 7ffed745ffc0 ip 
7f5b83ac1ebd sp 7ffed745ffc0 error 6 in 
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 7fffb59a8fd8 ip 
7f9972d4f3cb sp 7fffb59a8fd0 error 6 in 
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 7fffa7a92fe8 ip 
7f0f722d11fe sp 7fffa7a92ff0 error 6 in 
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 7ffc911c7fc8 ip 
7f1b3a047e4b sp 7ffc911c7fc0 error 6 in 
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 7ffe790b9ff8 ip 
7fcd75ed7e4b sp 7ffe790b9ff0 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

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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Baho utot 


On 5/8/19 3:49 PM, Ken Moffat wrote:

On Wed, May 08, 2019 at 11:46:40AM -0400, baho-u...@columbus.rr.com wrote:

I went back into my archive of LFS-8.2 and pulled out the perl-5.26.1.tar.xz
tarball and copied it into the build directory. Changed the script that I
use to build the chapter 5 tool chain to use that version and build the
package but not install it.  No segfault during the build.

Changed the script back to use perl-5.28.1 and the segfaults occur.

This points to something in the 5.28.1 version of perl causing the
segfaults.

Since I can not further debug this issue I may have to use the perl 5.26.1
version in my LFS-8.4 builds.

That is unless some one wants to help with this issue.

So, you are making some progress although it obviously does not feel
like that to you.

For the 5.26 series of perl, if my memory serves me well 5.26.3 has
a number of vulnerability fixes.

I also note that you said that using the pclinuxos *kernel* to run
LFS does not show the problem, which suggests a kernel-config
difference, or else a kernel-version difference.


No it does not segfault under pclinuxos as a host, only LFS.

I used the config file from pclinuxos which was 4.16.12 and did a make 
oldconfig then added the SATA drivers so it would boot.  It still 
segfaulted when building on LFS-8.4.   This is a perl or LFS issue as it 
will build under pclinuxos and arch linux.


I would say it could be an issue with my build but all tests pass and 
gcc tests are clean.


 The system runs fine, the version of perl in LFS-8.4 always segfaults 
under a LFS host.


Using the perl version from LFS-8.2 works fine under a LFS host.

It is my opinion that it is a LFS build/system issue.

Has any one else tried to build LFS-8.4 using the just build LFS-8.4?




ĸen

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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Bruce Dubbs 

On 5/8/19 12:00 PM, baho-u...@columbus.rr.com wrote:


On 5/8/19 10:08 AM, Pierre Labastie wrote:
Hey, why are you turning angry? People on this list are willing to 
help, but
they are not Harry Potter, and cannot fly to your machine to see what 
is going
on... They all told you they had not seen what you were seeing. This 
does not
mean you did something wrong, but it means they can only give general 
advice
about how to fix the issue. They can't experiment with this issue, 
since they
do not experience it... You may have hit a corner case that nobody of 
us has

hit before. Does it mean we deserve angry words?

Pierre


Grab my scripts/build system off github if you want to try my build.

This is not the first time that I have been told on this list that I am 
on my own.


I reported a problem.  The issue comes from using LFS to build itself, 
the build on the host system always works.


Here is the process:

build LFS on pclinuxos, working.

boot to the newly build LFS system

Use the same scripts and build LFS using the just built LFS. This has 
perl segfaulting.


Change the perl to version 5.26.1. This works.

Does any one here use LFS to build itself? 


Absolutely.  I've been doing that for 15 years.

Does your build fail if you are using jhalfs?

  -- Bruce


How would you validate that

the "system works" if you didn't.  It must be able to reproduce it self.

How else you you know that the LFS build process works correctly.

You can only know if it can rebuild it self.

That tells you that it built correctly and is working.




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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Ken Moffat 
On Wed, May 08, 2019 at 11:46:40AM -0400, baho-u...@columbus.rr.com wrote:
> 
> I went back into my archive of LFS-8.2 and pulled out the perl-5.26.1.tar.xz
> tarball and copied it into the build directory. Changed the script that I
> use to build the chapter 5 tool chain to use that version and build the
> package but not install it.  No segfault during the build.
> 
> Changed the script back to use perl-5.28.1 and the segfaults occur.
> 
> This points to something in the 5.28.1 version of perl causing the
> segfaults.
> 
> Since I can not further debug this issue I may have to use the perl 5.26.1
> version in my LFS-8.4 builds.
> 
> That is unless some one wants to help with this issue.

So, you are making some progress although it obviously does not feel
like that to you.

For the 5.26 series of perl, if my memory serves me well 5.26.3 has
a number of vulnerability fixes.

I also note that you said that using the pclinuxos *kernel* to run
LFS does not show the problem, which suggests a kernel-config
difference, or else a kernel-version difference.

ĸen
-- 
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
 - wiki.lspace.org/mediawiki/Music_With_Rocks_In


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread baho-utot 


On 5/8/19 10:08 AM, Pierre Labastie wrote:
Hey, why are you turning angry? People on this list are willing to 
help, but

they are not Harry Potter, and cannot fly to your machine to see what is going
on... They all told you they had not seen what you were seeing. This does not
mean you did something wrong, but it means they can only give general advice
about how to fix the issue. They can't experiment with this issue, since they
do not experience it... You may have hit a corner case that nobody of us has
hit before. Does it mean we deserve angry words?

Pierre


Grab my scripts/build system off github if you want to try my build.

This is not the first time that I have been told on this list that I am 
on my own.


I reported a problem.  The issue comes from using LFS to build itself, 
the build on the host system always works.


Here is the process:

build LFS on pclinuxos, working.

boot to the newly build LFS system

Use the same scripts and build LFS using the just built LFS. This has 
perl segfaulting.


Change the perl to version 5.26.1. This works.

Does any one here use LFS to build itself? How would you validate that 
the "system works" if you didn't.  It must be able to reproduce it self.


How else you you know that the LFS build process works correctly.

You can only know if it can rebuild it self.

That tells you that it built correctly and is working.


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Ken Moffat 
On Wed, May 08, 2019 at 07:02:15AM -0400, baho-u...@columbus.rr.com wrote:
> On 5/7/19 9:04 PM, Ken Moffat wrote:
> > 
> > Nothing odd in the perl logs ? (e.g. different results for tests in
> > configure between the two kernels, different actions in the build,
> > probably best identified by opening two term windows side-by-side on
> > a system where X is working).
> 
> I can not run two term windows side by side.  I have never been able to
> complete LFS because I could never get it to work sufficently to replace my
> current desktop system.  I have been building LFS off an on since LFS-5.0
> and maintain a repo. on github.
> 

I did not realise you had never completed a successful desktop build
(i.e. LFS and significant parts of BLFS).  Your past comments on
using rpm and putting things on github suggested you had a working
system.

Anyway - you don't need to be using LFS to look at logs: if the logs
are only on a partition used for LFS, mount that partition from the
distro system.

A more general approach to problems with getting a usable desktop
system - once LFS itself is bootable - is to ask about the problems
you encounter on blfs-support.  The LFS approach lends itself to
people trying to solve all their own problems, but that is not
always a productive approach.  Sometimes, other people can provide
useful insight.

ĸen
-- 
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
 - wiki.lspace.org/mediawiki/Music_With_Rocks_In


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread baho-utot 


I went back into my archive of LFS-8.2 and pulled out the 
perl-5.26.1.tar.xz tarball and copied it into the build directory. 
Changed the script that I use to build the chapter 5 tool chain to use 
that version and build the package but not install it.  No segfault 
during the build.


Changed the script back to use perl-5.28.1 and the segfaults occur.

This points to something in the 5.28.1 version of perl causing the 
segfaults.


Since I can not further debug this issue I may have to use the perl 
5.26.1 version in my LFS-8.4 builds.


That is unless some one wants to help with this issue.
--
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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread Pierre Labastie 
On 08/05/2019 13:02, baho-u...@columbus.rr.com wrote:
> On 5/7/19 9:04 PM, Ken Moffat wrote:
>> On Tue, May 07, 2019 at 05:50:28PM -0400, baho-u...@columbus.rr.com wrote:
>>> I have built a different kernel using pclinuxos config file.
>>>
>>> The segfaults only occur when building perl under LFS-8.4.  It does not stop
>>> or invalidate the build and the segfault error messages only go to the
>>> screen and to /var/log/sys.log.
>>>
>>> Here is some more info, if some one can decipher:
>>>
>>> May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip
>>> 0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5351]: segfault at 7ffc09fc7ff8 ip
>>> 0048bbbf sp 7ffc09fc7fe0 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5357]: segfault at 7fff3f7a0ff8 ip
>>> 0048bba6 sp 7fff3f7a1000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5359]: segfault at 7ffcbf3d2ff8 ip
>>> 005a8bc4 sp 7ffcbf3d3000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5365]: segfault at 7fff61303ff8 ip
>>> 005a8bc4 sp 7fff61304000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5375]: segfault at 7ffe31a01ff8 ip
>>> 0048c722 sp 7ffe31a02000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5377]: segfault at 7ffc7703efe8 ip
>>> 0048bbc9 sp 7ffc7703eff0 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5379]: segfault at 7ffd67853ff8 ip
>>> 0048ceb6 sp 7ffd67854000 error 6 in perl[407000+23]
>>> May  7 17:24:23 lfs kernel: perl[5385]: segfault at 7ffcff30dfa8 ip
>>> 0048dc3d sp 7ffcff30dfa0 error 6 in perl[407000+23]
>>> May  7 17:24:24 lfs kernel: perl[5389]: segfault at 7ffe0db99ff8 ip
>>> 7f8f708f1332 sp 7ffe0db9a000 error 6 in
>>> libc-2.29.so[7f8f70892000+142000]
>>>
>> I don't use gdb, but I think that using it would, at a minimum, mean
>> you need to know what command was being run.  These segfaults all
>> happened within about 1 second, but we have no indication of when the
>> various stages of the build happened, so no idea what this might have
>> been doing.
>>
>> Nothing odd in the perl logs ? (e.g. different results for tests in
>> configure between the two kernels, different actions in the build,
>> probably best identified by opening two term windows side-by-side on
>> a system where X is working).
> 
> I can not run two term windows side by side.  I have never been able to
> complete LFS because I could never get it to work sufficently to replace my
> current desktop system.  I have been building LFS off an on since LFS-5.0 and
> maintain a repo. on github.
> 
>> I will also mention that segfaults are not necessarily a bad thing -
>> see my experience with rustc, where system crashes (possibly, caused
>> by an -rc kernel) seemed to be associated with segfaults in the
>> syslog, and it was *much* later before I discovered that they were
>> actually intentional (a way to force something to die).  Similarly
>> for some of the tests in perl's testsuite.
>>
>> But since using a distro kernel apparently removed the problem, I
>> would be inclined to look at both the .config changes (both the
>> built-in items, and also whatever was loaded when you finished the
>> perl build) and also at the kernel versions (and theoretically any
>> non-upstream patches in the distro, if any).  But comparing the
>> kernels sounds a *lot* of work, with not much likelihood of a
>> result.  Ultimately, this might come down to : Your system ... your
>> problem :-(
> 
> Which is why I have never been able to actually use a LFS system.  Problems
> that I have had with LFS could not be solved or you could say I have never
> gotten much help trying to solve these issues on this mailing list.
> 
>> And for unexplained segfaults, memtest86 might also be useful - I
>> bought my main build machine about 3 years ago, up until Easter it
>> was running fine and then suddenly I started getting segfaults
>> building large programs (rustc, qt or qtwebengine) - I had 16GB RAM,
>> everything small still built fine).  Running memtest86 showed a
>> problem within 1 minute, one of the sticks had a problem.  Usually,
>> memtest86 takes a bit longer than that.  In that case, it still ran
>> after pulling one stick, and passed memtest.  It's now running ok
>> with a new stick.
> 
> 
> I would not expect it is my system as it builds without the segfaults under
> pclinuxos, it just fails while rebuilding its self.  Whne building under
> pclinuox the system is under heavy usage runing kde5 while building LFS.  I
> even have vlc and firefox open as well as 6 other windows and it uses most of
> the available memory.
> 
> 
> I am going to use/build an older perl to see if it segfaults.  If it does I am
> probably  finished with LFS at this
> point.  No m

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-08 Thread baho-utot 

On 5/7/19 9:04 PM, Ken Moffat wrote:

On Tue, May 07, 2019 at 05:50:28PM -0400, baho-u...@columbus.rr.com wrote:

I have built a different kernel using pclinuxos config file.

The segfaults only occur when building perl under LFS-8.4.  It does not stop
or invalidate the build and the segfault error messages only go to the
screen and to /var/log/sys.log.

Here is some more info, if some one can decipher:

May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip
0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5351]: segfault at 7ffc09fc7ff8 ip
0048bbbf sp 7ffc09fc7fe0 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5357]: segfault at 7fff3f7a0ff8 ip
0048bba6 sp 7fff3f7a1000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5359]: segfault at 7ffcbf3d2ff8 ip
005a8bc4 sp 7ffcbf3d3000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5365]: segfault at 7fff61303ff8 ip
005a8bc4 sp 7fff61304000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5375]: segfault at 7ffe31a01ff8 ip
0048c722 sp 7ffe31a02000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5377]: segfault at 7ffc7703efe8 ip
0048bbc9 sp 7ffc7703eff0 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5379]: segfault at 7ffd67853ff8 ip
0048ceb6 sp 7ffd67854000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5385]: segfault at 7ffcff30dfa8 ip
0048dc3d sp 7ffcff30dfa0 error 6 in perl[407000+23]
May  7 17:24:24 lfs kernel: perl[5389]: segfault at 7ffe0db99ff8 ip
7f8f708f1332 sp 7ffe0db9a000 error 6 in
libc-2.29.so[7f8f70892000+142000]


I don't use gdb, but I think that using it would, at a minimum, mean
you need to know what command was being run.  These segfaults all
happened within about 1 second, but we have no indication of when the
various stages of the build happened, so no idea what this might have
been doing.

Nothing odd in the perl logs ? (e.g. different results for tests in
configure between the two kernels, different actions in the build,
probably best identified by opening two term windows side-by-side on
a system where X is working).


I can not run two term windows side by side.  I have never been able to 
complete LFS because I could never get it to work sufficently to replace 
my current desktop system.  I have been building LFS off an on since 
LFS-5.0 and maintain a repo. on github.




I will also mention that segfaults are not necessarily a bad thing -
see my experience with rustc, where system crashes (possibly, caused
by an -rc kernel) seemed to be associated with segfaults in the
syslog, and it was *much* later before I discovered that they were
actually intentional (a way to force something to die).  Similarly
for some of the tests in perl's testsuite.

But since using a distro kernel apparently removed the problem, I
would be inclined to look at both the .config changes (both the
built-in items, and also whatever was loaded when you finished the
perl build) and also at the kernel versions (and theoretically any
non-upstream patches in the distro, if any).  But comparing the
kernels sounds a *lot* of work, with not much likelihood of a
result.  Ultimately, this might come down to : Your system ... your
problem :-(


Which is why I have never been able to actually use a LFS system.  
Problems that I have had with LFS could not be solved or you could say I 
have never gotten much help trying to solve these issues on this mailing 
list.




And for unexplained segfaults, memtest86 might also be useful - I
bought my main build machine about 3 years ago, up until Easter it
was running fine and then suddenly I started getting segfaults
building large programs (rustc, qt or qtwebengine) - I had 16GB RAM,
everything small still built fine).  Running memtest86 showed a
problem within 1 minute, one of the sticks had a problem.  Usually,
memtest86 takes a bit longer than that.  In that case, it still ran
after pulling one stick, and passed memtest.  It's now running ok
with a new stick.



I would not expect it is my system as it builds without the segfaults 
under pclinuxos, it just fails while rebuilding its self.  Whne building 
under pclinuox the system is under heavy usage runing kde5 while 
building LFS.  I even have vlc and firefox open as well as 6 other 
windows and it uses most of the available memory.



I am going to use/build an older perl to see if it segfaults.  If it 
does I am probably  finished 
with LFS at this point.  No more time for all the work with little to no 
result. I have thought about rebuilding LFS-8.2 which worked but at this 
point it is not worth the effort.



-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above in

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread Ken Moffat 
On Tue, May 07, 2019 at 05:50:28PM -0400, baho-u...@columbus.rr.com wrote:
> I have built a different kernel using pclinuxos config file.
> 
> The segfaults only occur when building perl under LFS-8.4.  It does not stop
> or invalidate the build and the segfault error messages only go to the
> screen and to /var/log/sys.log.
> 
> Here is some more info, if some one can decipher:
> 
> May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip
> 0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5351]: segfault at 7ffc09fc7ff8 ip
> 0048bbbf sp 7ffc09fc7fe0 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5357]: segfault at 7fff3f7a0ff8 ip
> 0048bba6 sp 7fff3f7a1000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5359]: segfault at 7ffcbf3d2ff8 ip
> 005a8bc4 sp 7ffcbf3d3000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5365]: segfault at 7fff61303ff8 ip
> 005a8bc4 sp 7fff61304000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5375]: segfault at 7ffe31a01ff8 ip
> 0048c722 sp 7ffe31a02000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5377]: segfault at 7ffc7703efe8 ip
> 0048bbc9 sp 7ffc7703eff0 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5379]: segfault at 7ffd67853ff8 ip
> 0048ceb6 sp 7ffd67854000 error 6 in perl[407000+23]
> May  7 17:24:23 lfs kernel: perl[5385]: segfault at 7ffcff30dfa8 ip
> 0048dc3d sp 7ffcff30dfa0 error 6 in perl[407000+23]
> May  7 17:24:24 lfs kernel: perl[5389]: segfault at 7ffe0db99ff8 ip
> 7f8f708f1332 sp 7ffe0db9a000 error 6 in
> libc-2.29.so[7f8f70892000+142000]
> 

I don't use gdb, but I think that using it would, at a minimum, mean
you need to know what command was being run.  These segfaults all
happened within about 1 second, but we have no indication of when the
various stages of the build happened, so no idea what this might have
been doing.

Nothing odd in the perl logs ? (e.g. different results for tests in
configure between the two kernels, different actions in the build,
probably best identified by opening two term windows side-by-side on
a system where X is working).

I will also mention that segfaults are not necessarily a bad thing -
see my experience with rustc, where system crashes (possibly, caused
by an -rc kernel) seemed to be associated with segfaults in the
syslog, and it was *much* later before I discovered that they were
actually intentional (a way to force something to die).  Similarly
for some of the tests in perl's testsuite.

But since using a distro kernel apparently removed the problem, I
would be inclined to look at both the .config changes (both the
built-in items, and also whatever was loaded when you finished the
perl build) and also at the kernel versions (and theoretically any
non-upstream patches in the distro, if any).  But comparing the
kernels sounds a *lot* of work, with not much likelihood of a
result.  Ultimately, this might come down to : Your system ... your
problem :-(

And for unexplained segfaults, memtest86 might also be useful - I
bought my main build machine about 3 years ago, up until Easter it
was running fine and then suddenly I started getting segfaults
building large programs (rustc, qt or qtwebengine) - I had 16GB RAM,
everything small still built fine).  Running memtest86 showed a
problem within 1 minute, one of the sticks had a problem.  Usually,
memtest86 takes a bit longer than that.  In that case, it still ran
after pulling one stick, and passed memtest.  It's now running ok
with a new stick.

ĸen
-- 
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
 - wiki.lspace.org/mediawiki/Music_With_Rocks_In


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread baho-utot 

I have built a different kernel using pclinuxos config file.

The segfaults only occur when building perl under LFS-8.4.  It does not 
stop or invalidate the build and the segfault error messages only go to 
the screen and to /var/log/sys.log.


Here is some more info, if some one can decipher:

May  7 17:24:23 lfs kernel: perl[5349]: segfault at 7fff0fb57ff8 ip 
0048ceb9 sp 7fff0fb58000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5351]: segfault at 7ffc09fc7ff8 ip 
0048bbbf sp 7ffc09fc7fe0 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5357]: segfault at 7fff3f7a0ff8 ip 
0048bba6 sp 7fff3f7a1000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5359]: segfault at 7ffcbf3d2ff8 ip 
005a8bc4 sp 7ffcbf3d3000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5365]: segfault at 7fff61303ff8 ip 
005a8bc4 sp 7fff61304000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5375]: segfault at 7ffe31a01ff8 ip 
0048c722 sp 7ffe31a02000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5377]: segfault at 7ffc7703efe8 ip 
0048bbc9 sp 7ffc7703eff0 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5379]: segfault at 7ffd67853ff8 ip 
0048ceb6 sp 7ffd67854000 error 6 in perl[407000+23]
May  7 17:24:23 lfs kernel: perl[5385]: segfault at 7ffcff30dfa8 ip 
0048dc3d sp 7ffcff30dfa0 error 6 in perl[407000+23]
May  7 17:24:24 lfs kernel: perl[5389]: segfault at 7ffe0db99ff8 ip 
7f8f708f1332 sp 7ffe0db9a000 error 6 in 
libc-2.29.so[7f8f70892000+142000]



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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread baho-utot 


On 5/7/19 1:48 PM, Ken Moffat wrote:

On Tue, May 07, 2019 at 08:24:11AM -0400, baho-u...@columbus.rr.com wrote:

Building perl ( both chapter 5 and 6 ) under the host system (pclinuxos)
works fine.

The issue is when I use the newly built LFS-8.4 to build its self ie as the
host system.

The perl build for both chapter 5 and chapter 6 produces some segfaults
outputs to stderr.

The build always completes and I when boot to this new build (lfs as the
host) and it works.


 From what you say, you have not captured stderr along with stdout
(i.e. 2>&1) and therefore you cannot say what the build was doing at
the time ?



Yes it was not captured


function Perl {
    #    Perl-5.28.1
    local pkg=perl-5.28.1.tar.xz
    local pkg_dir=${pkg%%.tar*}
    local logfile="${TOPDIR}/LOGS/tools-${FUNCNAME}.log"
    [ -e ${logfile}.complete ] && { msg "Skipping: ${FUNCNAME}";return 
0; } || msg "Building: ${FUNCNAME}"

    > ${logfile}
    pushd ${TOPDIR}/BUILD >> /dev/null 2>&1
        unpack "${pkg}"
        pushd ${pkg_dir} >> /dev/null 2>&1
            msg_line "    Configure: "
                sh Configure -des -Dprefix=/tools -Dlibs=-lm 
-Uloclibpth -Ulocincpth >> ${logfile} 2>&1

            msg_success
            msg_line "     Make: "
                make ${MKFLAGS} >> ${logfile} 2>&1
            msg_success
            msg_line "      Install: "
                cp -v perl cpan/podlators/scripts/pod2man /tools/bin >> 
${logfile} 2>&1

                mkdir -pv /tools/lib/perl5/5.28.1 >> ${logfile} 2>&1
                cp -Rv lib/* /tools/lib/perl5/5.28.1 >> ${logfile} 2>&1
            msg_success
        popd > /dev/null 2>&1
    popd > /dev/null 2>&1
    clean_build-directory
    mv ${logfile} ${logfile}.complete
    return
}




I've looked at screens where perl was building (with stdout and
stderr diverted to a log) several times in recent months - mainly
when the perl tests are running - and not seen this, nor is there
any sign of it in my build logs.

What I have seen are segmentation faults in my _system_ log.  I
think these are during the tests, and are expected.  But obviously
that doesn't apply to chapter 5.  Oh, and for the tests it is
obviously impractical to know which was running at the time (no
regular output until all tests have run).


I have not looked at the system log to see if the segfaults are there.

I have since built it using the host kernel and initrd image and it does 
not segfault.



I am going to build the kernel using the pclinuxos config file after I 
change it to add the SATA drivers as they are modules in their config file.






ĸen

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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread Ken Moffat 
On Tue, May 07, 2019 at 08:24:11AM -0400, baho-u...@columbus.rr.com wrote:
> Building perl ( both chapter 5 and 6 ) under the host system (pclinuxos)
> works fine.
> 
> The issue is when I use the newly built LFS-8.4 to build its self ie as the
> host system.
> 
> The perl build for both chapter 5 and chapter 6 produces some segfaults
> outputs to stderr.
> 
> The build always completes and I when boot to this new build (lfs as the
> host) and it works.
> 
From what you say, you have not captured stderr along with stdout
(i.e. 2>&1) and therefore you cannot say what the build was doing at
the time ?

I've looked at screens where perl was building (with stdout and
stderr diverted to a log) several times in recent months - mainly
when the perl tests are running - and not seen this, nor is there
any sign of it in my build logs.

What I have seen are segmentation faults in my _system_ log.  I
think these are during the tests, and are expected.  But obviously
that doesn't apply to chapter 5.  Oh, and for the tests it is
obviously impractical to know which was running at the time (no
regular output until all tests have run).

ĸen
-- 
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
 - wiki.lspace.org/mediawiki/Music_With_Rocks_In


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread Bruce Dubbs 

On 5/7/19 7:24 AM, baho-u...@columbus.rr.com wrote:
Building perl ( both chapter 5 and 6 ) under the host system (pclinuxos) 
works fine.


The issue is when I use the newly built LFS-8.4 to build its self ie as 
the host system.


The perl build for both chapter 5 and chapter 6 produces some segfaults 
outputs to stderr.


The build always completes and I when boot to this new build (lfs as the 
host) and it works.


The last LFS ( version 8.2 ) I built does not do this when using it to 
"rebuild its self".


Has anyone seen this?


I have not.  My development system is 8.4 plus a few updates (I just 
installed gcc9).  Generally I do not update LFS packages on my 
development system, but do use it to test LFS book package updates in a 
fresh chroot environment.  Since lfs-8.4, perl has only changed from 
5.28.1 to 5.26.2 and that is unlikely to have caused the type of changes 
you mention.


  -- Bruce


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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

2019-05-07 Thread Xi Ruoyao 
On 2019-05-07 08:24 -0400, baho-u...@columbus.rr.com wrote:
> Building perl ( both chapter 5 and 6 ) under the host system (pclinuxos) 
> works fine.
> 
> The issue is when I use the newly built LFS-8.4 to build its self ie as 
> the host system.
> 
> The perl build for both chapter 5 and chapter 6 produces some segfaults 
> outputs to stderr.
> 
> The build always completes and I when boot to this new build (lfs as the 
> host) and it works.
> 
> The last LFS ( version 8.2 ) I built does not do this when using it to 
> "rebuild its self".
> 
> Has anyone seen this?

I've never seen this.

I almost always build LFS on LFS (unless building on a machine w/o LFS
installed).  But I don't have a LFS-8.4 system because I always use development
LFS book.  So I can't confirm or disconfirm.
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

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