Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15287 > unrolled thread
| Started by | fireshen <shenyining@huawei.com> |
|---|---|
| First post | 2019-07-31 17:57 -0700 |
| Last post | 2019-07-31 17:57 -0700 |
| 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? fireshen <shenyining@huawei.com> - 2019-07-31 17:57 -0700
| From | fireshen <shenyining@huawei.com> |
|---|---|
| Date | 2019-07-31 17:57 -0700 |
| Subject | Re: memleak in execute_function? |
| Message-ID | <mailman.397.1564621014.1985.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web