Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15074 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-01 15:20 -0400 |
| Last post | 2019-07-01 15:20 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Large compound commands resulting in a segfault Chet Ramey <chet.ramey@case.edu> - 2019-07-01 15:20 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-01 15:20 -0400 |
| Subject | Re: Large compound commands resulting in a segfault |
| Message-ID | <mailman.4.1562016918.1967.bug-bash@gnu.org> |
On 6/21/19 3:22 PM, kfm@plushkava.net wrote: > Hi, > > The following script generates a compound command consisting of many instances of the : command. I have found that it reproducibly induces a segfault in all versions of bash from 2 onwards. I tested various other shells - several more than are implied here - all of which could handle the generated code without issue. It's an exceeded stack resource limit. Bash uses recursive function calls to implement command lists, and too many can exceed the stack limit. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web