Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16570

Re: Segfault in Bash

From Ilkka Virta <itvirta@iki.fi>
Newsgroups gnu.bash.bug
Subject Re: Segfault in Bash
Date 2020-07-14 19:02 +0300
Message-ID <mailman.203.1594742520.2306.bug-bash@gnu.org> (permalink)
References <CAH8yC8nB5fhvvdD1bCUsgNzNTni4ixkjDbfeKQLNVqZ71HpxBg@mail.gmail.com> <000a9512-7179-1379-4df0-ff256a105580@case.edu> <4865101b-a390-7833-87f8-f987db3823e2@iki.fi>

Show all headers | View raw


On 14.7. 16:08, Chet Ramey wrote:
> On 7/14/20 6:32 AM, Jeffrey Walton wrote:
>> ./audit-libs.sh: line 17: 22929 Segmentation fault      (core dumped)
>> $(echo "$file" | grep -E "*.so$")
> 
> Bash is reporting that a process exited due to a seg fault, but it is
> not necessarily a bash process.

As a suggestion: it might be useful if the error message showed the 
actual command that ran, after expansions. Here it shows the same 
command each time, and if only one of them crashed, you wouldn't 
immediately know which one it was. The un-expanded source line is in any 
case available in the script itself.

The message also seems to be much briefer for an interactive shell or a 
-c script. At least the latter ones might also benefit from the longer 
error message.

-- 
Ilkka Virta / itvirta@iki.fi

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


Thread

Re: Segfault in Bash Ilkka Virta <itvirta@iki.fi> - 2020-07-14 19:02 +0300

csiph-web