Re: v4.4 segfault in 'decode_prompt_string' when processing special parameter

From	Chris Schoenberg <chris@cr0ssbyte.com>
Newsgroups	gnu.bash.bug
Subject	Re: v4.4 segfault in 'decode_prompt_string' when processing special parameter
Date	2018-07-21 21:00 -0500
Message-ID	<mailman.4006.1532224865.1292.bug-bash@gnu.org> (permalink)
References	<CAAnqJ08xXw8Ezq4mn_FGojcx6vi26d001foWFncUJt809XiS_w@mail.gmail.com> <9b18593f-2068-a781-d869-23c725d1880a@case.edu> <CAAnqJ08xrVzsw3BPGfxxQoFkaSyEf4M0PHwcXWYwqiQeAV9bMQ@mail.gmail.com> <5a923099-2211-12b4-74f0-d0d022de8624@case.edu>

Show all headers | View raw

Thanks for taking the time to explain that :) I'll do more homework next
time

On Sat, Jul 21, 2018, 8:51 PM Chet Ramey <chet.ramey@case.edu> wrote:

> On 7/21/18 9:16 PM, Chris Schoenberg wrote:
> > Fair enough. Even though the behavior is different, the end is the same
> as
> > udf so makes sense of you want to leave it. Weird how it popped up in 4.4
> > though.
>
> The ${param@op} expansions were introduced in bash-4.4.
>
> --
> ``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 | Unroll thread

Thread

Re: v4.4 segfault in 'decode_prompt_string' when processing special parameter Chris Schoenberg <chris@cr0ssbyte.com> - 2018-07-21 21:00 -0500

csiph-web