On Wed, Mar 21, 2018 at 11:07:45AM -0300, Larissa Braz wrote:
> Hi,
>
> I found the following compilation error:
>
> xmalloc.c:51:14: error: conflicting types for ‘sbrk’
> extern char *sbrk();
> ^
> In file included from xmalloc.c:29:0:
> /usr/include/unistd.h:1043:14: note: previ
Hello,
Periodically we see bash processes which run in busy loops:
$ strace -fp 15264
strace: Process 15264 attached
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
rt_sigreturn({mask=[QUIT]}) = 143
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_M
Hi,
I'm using Bash version 4.1.2 on RedHat EL 6.8 (I realize these are old
releases).
In one of my bash scripts I have a here-document and at the end of
it's execution it will pop-up an gxmessage. My problem is that when
the here-document exits, the gxmessage closes.
Within the here-document I'
From: mabdulla
To: bug-bash@gnu.org
Subject: bash long prompt, color going past the end of prompt after
reaching bottom of terminal
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE=
How to reproduce bug:
calculate_prompt1(){
host="my-linux"
git_branch="a very very very very very very very very very very
very very very very long prompt"
prompt="@$host \\w : \[$(tput bold)$(tput setab 1)$(tput setaf
7)\]${git_branch}\[$(tput sgr0)\]\$ "
export PS1="$prompt"}
PR
On 3/22/18 1:44 PM, Musse Abdullahi wrote:
> Bash Version: 4.2
> Patch Level: 46
> Release Status: release
>
> Description:
> look at Repeat-By section
If the version information above is accurate, you should investigate
newer versions of bash. Version 4.2 is two major versions behind and
wa
On 22.3. 22:22, Chet Ramey wrote:
On 3/22/18 1:44 PM, Musse Abdullahi wrote:
Bash Version: 4.2
Patch Level: 46
Release Status: release
Description:
look at Repeat-By section
If the version information above is accurate, you should investigate
newer versions of bash. Version 4.2 is two m
On 3/22/18 3:38 PM, Andrei Vagin wrote:
> I am thinking how to fix this issue properly. Here are a few points:
> * bash should know that signals are ignored if a process is the init
> process in a pid namespace.
Why should it know this? It's not documented, not portable, and conflicts
with the wa
