Date: Sun, 29 Aug 1999 21:00:58 -0700 (PDT) From: Tim Vanderhoek <hoek@beast.cdrom.com> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/13463: /bin/sh: malloc() recursive call: segv Message-ID: <199908300400.VAA52728@beast.cdrom.com>
next in thread | raw e-mail | index | archive | help
>Number: 13463 >Category: bin >Synopsis: /bin/sh does not handle interrupts correctly (?) >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Aug 29 21:10:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Tim Vanderhoek >Release: FreeBSD 4.0-CURRENT alpha >Organization: FreeBSD Project >Environment: -stable (3.2-S) and -current, although seems easier to reproduce on -stable. >Description: $ while :; do echo -n ; done ^C $ while :; do echo -n ; done ^C $ while :; do echo -n ; done sh in malloc(): warning: recursive call. sh in malloc(): warning: recursive call. Segmentation fault (core dumped) >How-To-Repeat: As above, enter "while :; do echo -n ; done" repeatedly and interrupt it. When it does die, it dies immediately when the last while command is entered (ie. not at ^C). I suspect this is a more generic problem than this instance of it suggests. Sometimes 20 or more iterations must be completed before it finally segvs. Sometimes far fewer... >Fix: Hope you get lucky? >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?199908300400.VAA52728>