> Is this at the same point as the core dump in your previous message?
yes
> The initialize_shell_variables function is processing env. When the for
loop
> reaches env[16], glibc needs to use the main_arena.top variable. However,
the
> value in the address pointed to by the top variable is overwritten by
env[15],
> causing a glibc exception and resulting in a cor
> Hi. This appears to happen when creating a shell variable from the initial
> environment. I can't reproduce it. If you can find a way to reliably
> reproduce it, please let me know and we can work on it.
So far, we have encountered this issue three times in our environment. The
following is one
> Hi. This appears to happen when creating a shell variable from the initial
> environment. I can't reproduce it. If you can find a way to reliably
> reproduce it, please let me know and we can work on it.
I'm sorry, the environment is quite complex and I couldn't find a way to
reliably reproduc
Hi
A bash coredump has appeared in my environment, the stack information displayed
by GDB is as follows:
#0 __pthread_kill_implementation (threadid=
Hi
I found that there is a huge difference in performance between different
versions of bash when there are a large number of environment variables in my
system.
The steps to reproduce are as follows??
$ for i in `seq 1`; do export TEST_ENV_$i=$i; done
$ time echo `date`
In bash-4.3, it
hi
I accidentally copied a section of JSON text to the terminal and executed it,
which resulted in a system crash.Bash version is 5.1.8.
Later, I reproduced it and found that when I executed the following command,
the memory usage of bash became very large.
$
[{"key":"1","key":"1","key"
> First, systemd will send a sigterm to bash, but in bash-5.1, the bash
process will not be killed. this was caused by a > > > change in bash
5.1. The modified change information is as follows
> ```
> sss. Fix a bug where receiving SIGTERM from a different process while
readline was active could
Hello !
I am now doing a test on the fork bomb with the command `:(){:|:&};:` and
set `ulimit - c 1000`. And everything was well in bash-5.0, but there was a
problem in bash-5.1.
The main performance is that the system memory has been rising, and then the
kernel appears the oom, I found that
On 12/13/22 12:42 PM, wang yuhang wrote:> This modification has
been changed when dealing with '$(', It seems > to have missed the
right bracket. Maybe we should add this bracket.
It seems that there is something wrong with this patch, It's tru
Hello
In bash-5.2, There is one modification: fix to expand $'...' and
$"..." in certain word expansions while expanding lines of here-document data
This modification has been changed when dealing with '$(', It seems
to have missed the right bracket. Maybe we should add this bracket.
I hope
11 matches
Mail list logo
