Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15287 > unrolled thread

Re: memleak in execute_function?

Started byfireshen <shenyining@huawei.com>
First post2019-07-31 17:57 -0700
Last post2019-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.


Contents

  Re: memleak in execute_function? fireshen <shenyining@huawei.com> - 2019-07-31 17:57 -0700

#15287 — Re: memleak in execute_function?

Fromfireshen <shenyining@huawei.com>
Date2019-07-31 17:57 -0700
SubjectRe: 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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web