Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15287
| From | fireshen <shenyining@huawei.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: memleak in execute_function? |
| Date | 2019-07-31 17:57 -0700 |
| Message-ID | <mailman.397.1564621014.1985.bug-bash@gnu.org> (permalink) |
| References | <1564586812344-0.post@n7.nabble.com> <a691cf27-9017-5a0d-915b-c15b2765f591@case.edu> <1564621048237-0.post@n7.nabble.com> |
Yeah, I agree with your opinion, in the branch "if (subshell == 0) ", we have the function "maybe_restore_getopt_state" to free gs; however, in the branch "else", it seems like forget to free "gs", or we don't have to free it? -- Sent from: http://gnu-bash.2382.n7.nabble.com/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: memleak in execute_function? fireshen <shenyining@huawei.com> - 2019-07-31 17:57 -0700
csiph-web