Re: Memory leak in bash 4.3

gt; if (pflags & PF_ASSIGNRHS) > { > ! var = array_variable_part (name, &tt, (int *)0); > if (ALL_ELEMENT_SUB (tt[0]) && tt[1] == ']') > temp = array_value (name, quoted|Q_DOUBLE_QUOTES, 0, &atype, &ind); > Looks good, thank you! -- Jean Delvare SUSE L3 Support

Re: Memory leak in bash 4.3

On Mon, 15 Jun 2015 09:12:58 -0400, Chet Ramey wrote: > On 6/15/15 9:09 AM, Jean Delvare wrote: > > >> I made > >> this change back in October 2014 as part of an unrelated fix for an > >> array element quoting issue. > > > I'll submit an updated p

Re: Memory leak in bash 4.3

Hi Chet, Thanks for your reply. On Thu, 11 Jun 2015 10:54:31 -0400, Chet Ramey wrote: > On 6/9/15 3:42 PM, Jean Delvare wrote: > > > I think I have a minimal test case now: > > > > #!/bin/bash > > > > declare -a ARRAY > > > > ARRAY[0]=f

Re: Memory leak in bash 4.3

On Tue, 9 Jun 2015 18:02:31 +0200, Jean Delvare wrote: > I built bash 4.3.39 with --without-bash-malloc and then ran the daemon > under valgrind for 1 minute. The back trace for the leak is: > > 3,973 bytes in 430 blocks are definitely lost in loss record 1,610 of 1,613 >at 0x

Memory leak in bash 4.3

rnal (subst.c:2823) by 0x45859E: expand_word_list_internal (subst.c:2912) by 0x4360B7: execute_simple_command (execute_cmd.c:4000) I do not have a minimum test case yet, but I wanted to ask if the back trace above provides enough hints to recognize an already know bug and the commit that fixed it?

[PATCH] loadables/mkdir: Fix 3 warnings

octal = 0; } /* Make the new mode */ @@ -169,7 +167,7 @@ make_path (path, nmode, parent_mode) while (*p == '/') p++; - while (p = strchr (p, '/')) + while ((p = strchr (p, '/'))) { *p = '\0'; if (stat (npath, &sb) != 0) -- Jean Delvare SUSE L3 Support

Re: Memory leak in wait

Hi Chet, Le Thursday 05 March 2015 à 11:11 -0500, Chet Ramey a écrit : > On 2/28/15 5:29 AM, Jean Delvare wrote: > > > On Fri, 07 Nov 2014 08:24:07 -0500, Chet Ramey wrote: > >> On 11/7/14, 3:49 AM, Jean Delvare wrote: > >>> 2* If bash remembers the process

Re: Strange file -i

Hi Eric, Le Wednesday 04 March 2015 à 06:43 -0700, Eric Blake a écrit : > On 03/04/2015 01:44 AM, Jean Delvare wrote: > > Did you really intend to create an empty file named "-i" in > > http://git.savannah.gnu.org/cgit/bash.git/diff/?id=43aebe922bc2a614c410e282fdf772e

Strange file -i

Hi Chet, Did you really intend to create an empty file named "-i" in http://git.savannah.gnu.org/cgit/bash.git/diff/?id=43aebe922bc2a614c410e282fdf772e063454168 ? Thanks, -- Jean Delvare SUSE L3 Support

Re: Memory leak in wait

Hi Dave, On Mon, 2 Mar 2015 04:38:43 -0500, Dave Rutherford wrote: > On Mon, Mar 2, 2015 at 2:33 AM, Jean Delvare wrote: > > Which brings another question: is there any plan to implement sleep as > > a bash builtin? > > It's already available as a loadable builtin (

Re: Memory leak in wait

On Sat, 28 Feb 2015 11:29:14 +0100, Jean Delvare wrote: > I think we will stay away from background sleep and wait for now, and > instead use: > > read -t 1 -N 0 > > This was suggested by an lm-sensors user and as far as I can tell it > fits the bill with no downside

Re: Memory leak in wait

Hi Chet, Sorry for reviving an old discussion, I lost track back then. On Fri, 07 Nov 2014 08:24:07 -0500, Chet Ramey wrote: > On 11/7/14, 3:49 AM, Jean Delvare wrote: > > 2* If bash remembers the process statuses, how does one access the > >information? I couldn't find

Re: Memory leak in wait

Hi Chet, Thanks for the fast reply and the explanations, very appreciated. On Thu, 06 Nov 2014 20:57:11 -0500, Chet Ramey wrote: > On 11/6/14 8:09 AM, Jean Delvare wrote: > > A memory leak has been reported in a bash script I maintain [1]. After > > investigation, I was able to

Memory leak in wait

is a known problem? [1] http://lists.lm-sensors.org/pipermail/lm-sensors/2014-November/042913.html Thanks, -- Jean Delvare SUSE L3 Support

Re: Looking for a specific fix

Hi Chet, Le Tuesday 28 May 2013 à 15:31 -0400, Chet Ramey a écrit : > On 5/28/13 12:27 PM, Jean Delvare wrote: > > Hi all, > > > > There are a few changelog files seemingly related to bash on the web > > with the following entry: > > > > - change reset_job

Re: Looking for a specific fix

Le Tuesday 28 May 2013 à 18:27 +0200, Jean Delvare a écrit : > Hi all, > > There are a few changelog files seemingly related to bash on the web > with the following entry: > > - change reset_job_indices to avoid infinite looping when js.j_firstj > == 0 or js.j_firstj

Looking for a specific fix

ANGES file of bash-4.0. So I have a hard time figuring out if this corresponds to an actual fix in bash. Can anyone shed some light on this, and ideally point me to the code change if it exists somewhere? Thanks, -- Jean Delvare Suse L3