on kernels 3.14.8 and 3.16.6
I'm hoping someone can help me narrow down the issue to find out what we
are doing wrong. The problem seems to have been there since we upgraded to
bash 4.3.
Happy to give more information and try things out.
Kind Regards
Scott.
On Fri, Feb 20, 2015 at 09:08:30AM -0500, Chet Ramey wrote:
On 2/20/15 6:56 AM, Scott wrote:
Hi,
When we run the bash unittests on some system we occasionally get a error
in the varenv3.sub script.
./varenv3.sub: cannot open named pipe /tmp/bash_tests.8150/sh-np-5140328
for writing: No such
particular bug in it.
Regards,
Scott.
--PREVIOUS MESSAGE FOR
REFERENCE
From: scotty.mcmil...@gmail.com
To: bug-bash@gnu.org
Subject: Brace expansion infinite loop, memory corruption, and other bugs.
Configuration Information [Aut
I'm running Fedora core 3 on an Athlon, and I get the following problem:
I get an error when running:
echo $(( 008 / 2 ))
In my script, however, I'm passing the value as a variable. when it
gets to 008, I get an error.
see below for my version and such:
[EMAIL PROTECTED] complex]$ echo $(( 001
After running /configure --exec-prefix=/bin (also tried
--prefix=/bin), make succeeds, but sudo make install fails:
...
fi
/usr/bin/install -c -m 0755 bash /bin/bin/bash
/usr/bin/install -c -m 0555 bashbug /bin/bin/bashbug
( cd ./doc ; make \
man1dir=/usr/local/man/man1 man1ext=.1 \
Please let me know if more info would help. Again, I hope this is
helpful, or at least isn't extremely annoying, and I apologize if it
isn't/is.
Scott
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Paul Jarc spake thusly on 07/11/2007 12:10 PM:
Scott Carpenter <[EMAIL PROTECTED]> wrote:
V="one/two"
[[ ! $V =~ ^\.*/ ]] && echo not
3.1 will remove the backslash as part of basic string parsing, just as
if this were not part of a [[ command, while 3.2 handles the ar
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='b
ter even if the input doesn't have one, as is
extremely common (perhaps even universal). At the very
least I think an option should be present to turn on this
behavior for the builtin, because I can see some cases where
one *would* want the behavior as implemented as well.
What do people think of this?
Thanks.
--
Scott
s not
saving the `logout' in history.)
...
I believe this shows the bug. I suggest zeroing
`history_lines_after_session' upon "history -c" OR having
`force_append_history' cause it to do just that in
`maybe_append_history()' in addition to `maybe_save_history()'
as it does already.
Please keep me copied as I am not on the list. Thanks.
--
Scott
803fb894280773f16f2deb
Author: Chet Ramey
Date: Mon Jan 7 09:27:52 2019 -0500
bash-5.0 distribution sources and documentation
Thank you to Chet and to everyone for their time working on Bash!
Scott
ay, but it will become
> easier to identify the corresponding changesets.
Thank you for the explanation, Koichi. I thought I had bisected on devel
but perhaps I did something wrong.
I can attempt another bisect at some point in the future, but these days
it is very difficult for me to find time.
Thanks for your quick reply!
Scott
On Tue, Oct 27, 2020 at 09:40:53AM -0400, Chet Ramey wrote:
> On 10/27/20 12:11 AM, Scott Kostyshak wrote:
> > The following example uses more peak RAM on new bash versions than old
> > versions:
> >
> > for i in {1..100}; do
> > echo "${i}" &g
While compiling Bash, I couldn't help but notice that all over GNU's website it
is spelled with a capital B. However, when I tried to compile Bash, I noticed a
message that said "GNU bash, version 4.3.30(1)-release (i686-pc-linux-gnu)" in
a box surrounded by stars. Why is the B not capitalized h
to
parallel versions that run pretty fast on a parallel filesystem.
Enjoy,
-- Scott
x27;echo first' (full output below).
Why is the second invocation ignored? Maybe a bug?
I see this behavior on 3.2.57 and 4.2.45. Thanks,
- Scott
Example run:
~$echo 'trap "echo $1" DEBUG' > trapcmd
~$source ./trapcmd first
first
first
~$source ./
trap 'echo first' DEBUG" > script1
echo "trap 'echo second' DEBUG" > script2
. ./script1
. ./script2
I would expect the trap calls in script1 and script2 to behave
identically. Instead, script1's trap is set, but script2's trap is
ignored.
Thanks for the reply.
- Scott
x27;t try with any other traps. Maybe it's specific to DEBUG.)
Yep. I haven't tried with any traps other than DEBUG, just because
that's the only trap my script needs. If the maintainers would like
more information about affected traps, I'm happy to investigate.
- Scott
lready set or not? If that's
expected behavior,
I would certainly like to document it!
Thanks,
- Scott
d restore.
Just curious: why not restore the state of emptiness that
existed before? Why treat these two states differently?
(presence of trap vs. absence of trap)
Other than this minor question, your explanation makes
total sense. Thanks Chet.
- Scott
20 matches
Mail list logo