bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SIGSEGV in GNU bash, version 5.1.4(1)-release (sparc-sun-solaris2.10


From: Chet Ramey
Subject: Re: SIGSEGV in GNU bash, version 5.1.4(1)-release (sparc-sun-solaris2.10)
Date: Wed, 30 Dec 2020 19:31:17 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.6.0

On 12/29/20 7:28 PM, Dennis Clarke wrote:

Firstly as a minor nit that seems to re-appear yearly there are still
source files in the release tarballs that are not readable to a normal
user :

#
#  find . -ls | grep '\-\-\-'
7348095   24 -rw------- 1 286 staff 38962 Jul  8 14:19 ./lib/malloc/malloc.c
7347442    1 -rw------- 1 286 staff   226 May 29  2020 ./tests/varenv20.sub
#
# chmod 644 ./lib/malloc/malloc.c  ./tests/varenv20.sub

Trivial but annoyed as it throws the compile process out the window on
the first initial pass.  Otherwise all goes well until we try to use the
resultant bash binary.

I'll change those. A minor annoyance at best.


I was very surprised to see :

alpha $
alpha $ dbx /opt/bw/bin/bash
node_alpha-host_sun4u-zone_z_003-time_1609232628-pid_10009-uid_16411-gid_20002-fid_bash.core
Reading bash
core file header read successfully
Reading ld.so.1
Reading libreadline.so.8
Reading libhistory.so.8

I can't reproduce this with the default configure and build options, on a
fresh install of Solaris 10 1/13 on Virtualbox. Maybe try building without
linking with an external readline library. There may be some
incompatibility between readline-8.0 and 8.1 that I'm not aware of.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]