Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15286 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-31 19:19 -0400 |
| Last post | 2019-07-31 19:19 -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: memleak in execute_function? Chet Ramey <chet.ramey@case.edu> - 2019-07-31 19:19 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-31 19:19 -0400 |
| Subject | Re: memleak in execute_function? |
| Message-ID | <mailman.394.1564615199.1985.bug-bash@gnu.org> |
On 7/31/19 11:26 AM, fireshen wrote: > Hey all, > > I suspect there is a memleak in bash. > > I use the bash 4.4.23 (fedora Linux) with ASAN. Then I run some testcases > and find a memleak. It's not a memory leak. It's a false positive from asan or valgrind. The `gs' object is freed by maybe_restore_getopt_state or a function it calls (sh_getopt_dispose_istate via sh_getopt_restore_istate). -- ``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