Date: Tue, 19 Nov 2002 13:43:35 +0100 (CET) From: Oliver Fromme <olli@secnetix.de> To: FreeBSD-gnats-submit@FreeBSD.org Cc: Oliver Fromme <olli@fromme.com> Subject: bin/45478: /bin/sh coredump Message-ID: <200211191243.gAJChZLU073555@lurza.secnetix.de>
next in thread | raw e-mail | index | archive | help
>Number: 45478 >Category: bin >Synopsis: /bin/sh coredump >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 19 04:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Oliver Fromme >Release: FreeBSD 4.7-RELEASE i386 >Organization: secnetix GmbH & Co KG, http://www.secnetix.de/ >Environment: System: FreeBSD 4.7-RELEASE I could also reproduce the very same problem on 4.6 and even on 4.4, so it seems to be a long-standing problem. >Description: $ /bin/sh $ while for true; do false; done; do true; done ^C $ set -E sh in malloc(): warning: recursive call sh in malloc(): warning: recursive call Segmentation fault (core dumped) >How-To-Repeat: See above. The problem is not 100% reproducible. Sometimes it happens immediately, sometimes it takes 20+ attempts, but sooner or later it'll crash. I guess it depends on when exctly you interrupt the endless while loop. I can also provide the core dump if necessary. >Fix: Sorry, none known. I suggest someone familiar with the innards of our sh looks at it. It's probably easy to track down, using /etc/malloc.conf and the core dumps ... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211191243.gAJChZLU073555>