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


Groups > gnu.bash.bug > #16570

Re: Segfault in Bash

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Ilkka Virta <itvirta@iki.fi>
Newsgroups gnu.bash.bug
Subject Re: Segfault in Bash
Date Tue, 14 Jul 2020 19:02:26 +0300
Lines 21
Approved bug-bash@gnu.org
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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 7bit
X-Trace usenet.stanford.edu 1594742521 16379 209.51.188.17 (14 Jul 2020 16:02:01 GMT)
X-Complaints-To action@cs.stanford.edu
To chet.ramey@case.edu, noloader@gmail.com, bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
In-Reply-To <000a9512-7179-1379-4df0-ff256a105580@case.edu>
Content-Language en-US
X-SASI-RCODE 200
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; h=subject:to:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=smtp; bh=IPds3J8wRbhC4kjkjEkheu7V/fylyDF32B8co1EsQAY=; b=I6BZJ3/CFSUR4u58Kx/qfQYTIvKJJDCsKpQIfsoJPBAWA8LRBDEtO79PFNXIS7My2tI9U+yAPYgOIjKwAiwfD4M+1x71nBd+TyiRbZEfvHlconwv+z9bfQmMFxjs5gSKmjR0JfFu3ov4p4ZGl2UQB9ARg+iY1VQ/p6gp83ohNhytvJqD5iwBDyCFit0Jaslu1Q8v89GDbo5sCmw+35yHhzd7wOhHK0VU/GBEXb1cmZyCgbkdW6DtbSPyw09QDr6tHnMA/QumyjbLJKrOtHWeT61HK4/KX2IA4jRK3aY3cEti2j2MJoB+YKDWpexXvo+Cw4P6qZu8O3+BoLbw+SmkRw==
Received-SPF neutral client-ip=157.24.2.104; envelope-from=itvirta@iki.fi; helo=smtp-in-2.cc.lut.fi
X-detected-operating-system by eggs.gnu.org: First seen = 2020/07/14 11:54:39
X-ACL-Warn Detected OS = FreeBSD 8.x
X-Spam_score_int -31
X-Spam_score -3.2
X-Spam_bar ---
X-Spam_report (-3.2 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action no action
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <4865101b-a390-7833-87f8-f987db3823e2@iki.fi>
X-Mailman-Original-References <CAH8yC8nB5fhvvdD1bCUsgNzNTni4ixkjDbfeKQLNVqZ71HpxBg@mail.gmail.com> <000a9512-7179-1379-4df0-ff256a105580@case.edu>
Xref csiph.com gnu.bash.bug:16570

Show key headers only | 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