Re: Seg fault on "echo ~nosuchuser"

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Seg fault on "echo ~nosuchuser"
Date	2020-06-01 15:12 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.939.1591038736.2541.bug-bash@gnu.org> (permalink)
References	(1 earlier) <0c4fcd5b-3ac6-ea8c-e537-b4bfc9215de4@case.edu> <CAAHpriN1QYMAHOqAKHr=yOJF-0tiiKDnzqawXh+DYxP7=wrDiA@mail.gmail.com> <81924c39-6cde-617b-c5a7-5e3605e0c3b8@case.edu> <CAAHpriP=25drsYLtrOti2-fYEFjNpm76sAVskiVxUdthEB0vjw@mail.gmail.com> <6e7b8282-c41a-15b8-0dbf-9f811f6c3eee@case.edu>

Show all headers | View raw

On 6/1/20 3:04 PM, Keith Thompson wrote:

>     OK, that's half of it.
> 
>     If you have a chance, can you verify that the problem exists with the
>     bash-20200520 push?
> 
>     http://git.savannah.gnu.org/cgit/bash.git/snapshot/bash-ce1a3c07c4e17ed176edccd75892dfcf8242de60.tar.gz
> 
> 
> Confirmed, the problem does exist with that version. 

I finally found a case where 16-byte alignment for memory returned by
malloc() is required. But it's only on Linux systems that use systemd.
I bet it's trying to marshal arguments for IPC and uses instructions
that require 16-byte alignment.

Thanks for your help verifying this.

Chet
-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Seg fault on "echo ~nosuchuser" Chet Ramey <chet.ramey@case.edu> - 2020-06-01 15:12 -0400

csiph-web