On 6/2/16 2:25 AM, konsolebox wrote:
> On Thu, Jun 2, 2016 at 1:12 PM, Matthias Zimmerman
> wrote:
>> a better example is
>> cat <(su) | cat
>> cat <([a very simple program that will block io]) | (any thing else)
$ cat <(sudo cat) | cat
[sudo] password for chet:
^C
$ cat <(sudo cat) | cat
^C
$ ec
On Thu, Jun 2, 2016 at 1:12 PM, Matthias Zimmerman
wrote:
> a better example is
> cat <(su) | cat
> cat <([a very simple program that will block io]) | (any thing else)
Ok, it does crash.
Next time, please send your message to bug-bash@gnu.org as well.
--
konsolebox
On Sun, May 29, 2016 at 1:17 PM, Matthias Zimmerman
wrote:
> I found a bug in bashes redirection?
> anyway the recipe for disaster is,
>
> cat <(sudo {any command}) | {any other command}
>
> And if you ctl-C it/ try to kill it, bash will die
What command do you use, and what version of bash? Min
On Thu, Dec 17, 2015 at 2:02 AM, Chet Ramey wrote:
> On 12/14/15 2:52 AM, Piotr Grzybowski wrote:
>> Hey,
>>
>> [..] solved the issue by --without-bash-malloc which could indicate a bug or
>> lack of
>> proper support in lib/malloc/malloc.c for his platform. However, we
>> were unable to get more
On 12/14/15 2:52 AM, Piotr Grzybowski wrote:
> Hey,
>
> we have had an off--list discussion with Kai on this (to shorten the
> 30 mails we exchanged ;-) I am writing this summary). He solved the
> issue by --without-bash-malloc which could indicate a bug or lack of
> proper support in lib/malloc/
Hey,
we have had an off--list discussion with Kai on this (to shorten the
30 mails we exchanged ;-) I am writing this summary). He solved the
issue by --without-bash-malloc which could indicate a bug or lack of
proper support in lib/malloc/malloc.c for his platform. However, we
were unable to get
rzybowski [mailto:narsil...@gmail.com]
> Sent: 2015年10月23日 15:34
> To: Kai Wang X
> Cc: chet.ra...@case.edu; Aharon Robbins; bug-bash@gnu.org
> Subject: Re: Bash crash
>
> I would run the same script under gdb (in the similar manner as you examine
> the core in the case of
-Original Message-
From: Piotr Grzybowski [mailto:narsil...@gmail.com]
Sent: 2015年10月23日 15:34
To: Kai Wang X
Cc: chet.ra...@case.edu; Aharon Robbins; bug-bash@gnu.org
Subject: Re: Bash crash
I would run the same script under gdb (in the similar manner as you examine
the core in th
Message-
> From: Piotr Grzybowski [mailto:narsil...@gmail.com]
> Sent: 2015年10月23日 1:08
> To: Kai Wang X
> Cc: chet.ra...@case.edu; Aharon Robbins; bug-bash@gnu.org
> Subject: Re: Bash crash
>
> do I understand correctly, that when you comment the line 187 the issue is
> not exi
Grzybowski [mailto:narsil...@gmail.com]
Sent: 2015年10月23日 1:08
To: Kai Wang X
Cc: chet.ra...@case.edu; Aharon Robbins; bug-bash@gnu.org
Subject: Re: Bash crash
do I understand correctly, that when you comment the line 187 the issue is not
existent?
cheers,
pg
On Thu, Oct 22, 2015 at 4:39 AM, Kai Wang X w
From: Piotr Grzybowski [mailto:narsil...@gmail.com]
> Sent: 2015年10月21日 19:27
> To: Kai Wang X
> Subject: Re: Bash crash
>
> hello,
>
> does the problem also appear on other pieces of equipment? I mean, different
> phisical machine, of the same sort?
>
> pg
>
>
&g
On Thu, Oct 22, 2015 at 02:39:43AM +, Kai Wang X wrote:
> The process named "com" launched by script command "com.sh start". Pls refer
> to the attached files. It looks easy, doesn't it?
It looks like a horrible mish-mash of legacy Bourne shell syntax,
edited later by another person using cer
ility of the issue.
-Original Message-
From: Piotr Grzybowski [mailto:narsil...@gmail.com]
Sent: 2015年10月21日 19:27
To: Kai Wang X
Subject: Re: Bash crash
hello,
does the problem also appear on other pieces of equipment? I mean, different
phisical machine, of the same sort?
pg
On Wed
t;From: Chet Ramey [mailto:chet.ra...@case.edu]
>Sent: 2015å¹´10æ20æ¥ 21:31
>To: Kai Wang X; bug-bash@gnu.org
>Cc: chet.ra...@case.edu
>Subject: Re: Bash crash
>
>On 10/19/15 10:47 PM, Kai Wang X wrote:
>> Dear,
>>
>>
>>
>> We have two product
On 10/20/15 10:29 PM, Kai Wang X wrote:
> Hi Chet,
>
> Thank you for your response.
>
> But it does not make sense since sbrk failure will be checked:
>
> mp = (union mhead *) sbrk (sbrk_amt);
>
> /* Totally out of memory. */
> if ((long)mp == -1)
> goto morecore_done;
Sure, sbrk fai
reproduce
in my environment. Only every few times of my equipment booting up, it
generates a coredump file.
-Original Message-
From: Chet Ramey [mailto:chet.ra...@case.edu]
Sent: 2015年10月20日 21:31
To: Kai Wang X; bug-bash@gnu.org
Cc: chet.ra...@case.edu
Subject: Re: Bash crash
On 10/19/15 10
On 10/19/15 10:47 PM, Kai Wang X wrote:
> Dear,
>
>
>
> We have two products which are using bash 4.2 and 4.3 separately. They all
> meet bash crash issue. Please refer to the attached files.
>
> It is hard for me to understand the bash source code to find the root cause
> out.
It really look
On 2/24/13 11:59 PM, phil colbourn wrote:
> Bash Version: 4.2
> Patch Level: 37
> Release Status: release
>
> Description:
>
> Within (( )), 'b=b+1' will crash bash with a segment fault if it follows an
> array read such as 'a=X[b]'.
Thanks for the report and the test case. This was reported p
18 matches
Mail list logo
