Well, the recent version runs ok, I just wan't to find the commit solving this
bug.
Thanks,
Zongyong Wu
-邮件原件-
发件人: Eduardo Bustamante [mailto:dual...@gmail.com]
发送时间: 2017年5月11日 22:39
收件人: wuzongyong (A)
抄送: bug-bash@gnu.org; Wanzongshun (Vincent)
主题: Re: memory leak in bash
On Thu,
On 5/11/17 10:56 AM, Steve Volumetric wrote:
> In addition to my previous email, I also tired older versions of bash,
> going back to 4.2
>
> I get the exact same error with all of them with the only exception being
> that the error occurs on different lines, but it always boils down to this:
>
>
Hello,
I get the configure script to accept --enable-static-link seemingly without
issue.
I'm using gcc 6.1.0 and when I do 'make' I get:
rm -f mksyntax
gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"x86_64"'
-DCONF_OSTYPE='"linux-gnu"' -DCONF_MACHTYPE='"x86_64-unknown-linux-gnu"'
-DCONF_VENDOR='"un
In addition to my previous email, I also tired older versions of bash,
going back to 4.2
I get the exact same error with all of them with the only exception being
that the error occurs on different lines, but it always boils down to this:
./config.h:332:22: error: two or more data types in declar
On 5/11/17 10:42 AM, Eduardo Bustamante wrote:
> On Thu, May 11, 2017 at 9:31 AM, Chet Ramey wrote:
> [...]
>> Yes, this is it. I fixed it yesterday.
>
> Thanks. From the crashing inputs that I reported, is there any that is
> still unfixed that I can help with? When are you going to upload the
>
On Thu, May 11, 2017 at 9:31 AM, Chet Ramey wrote:
[...]
> Yes, this is it. I fixed it yesterday.
Thanks. From the crashing inputs that I reported, is there any that is
still unfixed that I can help with? When are you going to upload the
next snapshot? (To see if I can resume fuzzing next weekend
On Thu, May 11, 2017 at 3:47 AM, wuzongyong (A) wrote:
[...]
> My bash version is version 4.2.46(1)-release, valgrind version is 3.11.0 ,
> could someone help to tell me if it is a bug please? And I wanna to know the
> deeply level reason.
Try with a more recent version. Version 4.2.46 is a f
On 5/11/17 8:03 AM, Eduardo Bustamante wrote:
> On Tue, May 9, 2017 at 9:28 AM, Eduardo Bustamante wrote:
> [...]
>
> From what I can tell, it seems like the problem is that `set-mark'
> allows you to set a negative rl_mark, and then you can use
> `exchange-point-and-mark' to place that negative
Hi,
I met a memory leak to use valgrind run shell code below:
#! /bin/bash
rc_exit ()
{
exit 0
}
rc_exit
And the valgrind log just like that:
HEAP SUMMARY:
==27459== in use at exit: 21,968 bytes in 464 blocks
==27459== total heap usage: 568 allocs, 104 frees, 29,714 bytes allocated
==2745
On Tue, May 9, 2017 at 3:28 PM, Chet Ramey wrote:
[...]
> This would be a great project for someone who wanted to help.
Thanks. I'll familiarize myself with the tools and try to send a patch.
The C with acute accent character: https://en.wikipedia.org/wiki/%C4%86
- Upper case
dualbus@debian:~$ printf '\U0106\n'
Ć
- Lower case
dualbus@debian:~$ printf '\U0107\n'
ć
Now, in bash, if you type in ć, then run readline `upcase-word' on it,
instead of ending up with the UTF-8 multibyte strin
On Tue, May 9, 2017 at 9:28 AM, Eduardo Bustamante wrote:
[...]
>From what I can tell, it seems like the problem is that `set-mark'
allows you to set a negative rl_mark, and then you can use
`exchange-point-and-mark' to place that negative rl_mark into
rl_point.
A simple way of breaking this is
On Wed, May 10, 2017 at 8:52 PM, Pierre Gaston wrote:
> See:
> https://lists.gnu.org/archive/html/bug-bash/2012-11/msg00040.html[https://lists.gnu.org/archive/html/bug-bash/2012-11/msg00040.html]
> Pierre
> PS: I'm with you ;)
Thanks for the link, I didn't find it in my earlier searches.
Well,
13 matches
Mail list logo
