Re: Seg fault on "echo ~nosuchuser"

From	Ángel <angel@16bits.net>
Newsgroups	gnu.bash.bug
Subject	Re: Seg fault on "echo ~nosuchuser"
Date	2020-06-02 01:58 +0200
Message-ID	<mailman.962.1591055923.2541.bug-bash@gnu.org> (permalink)
References	(2 earlier) <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> <1591055912.1057.9.camel@16bits.net>

Show all headers | View raw

On 2020-06-01 at 15:12 -0400, Chet Ramey wrote:
> 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

You mean that with systemd getpwnam() crashes if using a malloc() that
returns addresses not 16-byte aligned?

Cornercase, surely, but it seems like a bug in whatever is assuming such
alignment. That's not even pointer-size alignment.

Cheers

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

Thread

Re: Seg fault on "echo ~nosuchuser" Ángel <angel@16bits.net> - 2020-06-02 01:58 +0200

csiph-web