Re: accessing ENVIRON causes SIGFPE when first var is numeric

[arnold]

Andy's fix is in the repo. Thanks for the report.

Arnold

"David Arroyo" <david@aqwari.net> wrote:

> On Wed, Jun 15, 2022, at 14:56, arnold@skeeve.com wrote:
> > Wolfgang Laun <wolfgang.laun@gmail.com> wrote:
> >
> >> SETENV(3) appears to be the function that determines what may or may not be
> >> in the Environment. From the man page's ERROR section: EINVAL name is NULL,
> >> points to a string of length 0, or contains an '=' character. Names weirder
> >> than a digit should be possible.
> >>
> >> Wolfgang
> >
> > So 0=foo is apparently valid, but will probably give shells a fit.
>
> Good to know. I looked and found that the variable was set by
> the `exec` command of the `execline` suite of tools[1], which I
> wrote my startup script in.
>
> And I've verified that Andy's patch resolves the issue.
>
> Thanks again,
> David
>
> [1]: https://skarnet.org/software/execline/