Hello, I want to file a bug in bash.
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security
-Wall
From: Saint Michael
Date: Sat, Oct 12, 2024 at 9:49 AM
Subject: New feature
The command printf needs a new flag, -e, that would mimic that way the
same flag works with echo.
After using printf, right now I need to lunch a second command if I
need to expand the \n into real new lines
Anybody else with the knowledge to tackle this?
I am not capable of even writing C code correctly.
On Fri, Jun 21, 2024 at 4:22 PM Chet Ramey wrote:
>
> On 6/21/24 3:59 PM, alex xmb sw ratchev wrote:
>
> > > If floating point math support is added to bash, I would expect it to
> > > be
in this code:
data="'1,2,3,4','5,6,7,8'"
# Define the processing function
process() {
echo "There are $# arguments."
echo "They are: $@"
local job="$1"
shift
local a="$1"
shift
local b="$1"
shift
local remaining="$*"
echo "Arg1: '$a', Arg2: '$b'"
}
process "$dat
Great idea.
On Fri, Jun 14, 2024 at 3:18 AM Léa Gris wrote:
>
> Le 14/06/2024 à 03:41, Martin D Kealey écrivait :
> > On Thu, 13 Jun 2024 at 09:05, Zachary Santer wrote:
> >
> >>
> >> Let's say, if var is in the form of a C floating-point literal,
> >> ${var@F} would expand it to the locale-depe
I think that we should go ahead and do it.
On Wed, Jun 12, 2024, 5:06 PM Zachary Santer wrote:
> On Thu, Jun 6, 2024 at 6:34 AM Léa Gris wrote:
> >
> > Le 06/06/2024 à 11:55, Koichi Murase écrivait :
> >
> > > Though, I see your point. It is inconvenient that we cannot pass the
> > > results of
I think that we should do this in the shell. I mean. It will get done at
some point, in the next decades or centuries. Why not do it now? Let's
compile some C library or allow inline C
On Wed, Jun 5, 2024, 2:12 PM Greg Wooledge wrote:
> On Wed, Jun 05, 2024 at 01:31:20PM -0400, Saint
the most obvious use of floating variables would be to compare
balances and to branch based on if a balance is lower than a certain
value
I use:
t=$(python3 -c "import math;print($balance > 0)")
and the
if [ "$t" == "False" ];then
echo "Result <= 0 [$t] Client $clname $clid Balance $balance"
fi
The
>
> It's time to add floating point variables and math to bash.
It just makes so much easier to solve business problems without external
calls to bc or Python.
Please let's overcome the "shell complex". Let's treat bash a real language.
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall
uname output: Linux nb 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1
(2024-04-11) x86_
I support this feature.
On Sat, Nov 11, 2023, 11:29 AM Corto Beau wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> uname output: Linux zinc 6.6.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 08
>
It seems to me that Autoconf (configure) is making some bad choices if
it is just guessing that support exists like that, especially when it
has a guaranteed fallback. It's job is to setup the build for the
target host system. I was able to fix the build by using
--without-bash-malloc. Simpl
I was trying to cross-compile bash for musl libc. The configure script reports:
checking for working sbrk... configure: WARNING: cannot check working sbrk if
cross-compiling
yes
However, I don't believe musl libc supports sbrk. However, autoconf seems to
default
to assuming yes and sets the H
ote that libcurses links to libxcurses.
Michael
There is an additional problem with IFS and the command read
Suppose I have variable $line with a string "a,b,c,d"
IFS=',' read -r x1 <<< $line
Bash will assign the whole line to x1
echo $x1
line="a,b,c,d";IFS=',' read -r x1 <<< $line;echo $x1;
a,b,c,d
but if I use two variables
line="a,b,c,d";I
He has a point, though. To have some of the functionality of jq inside Bash
may be very useful.
If he can supply a patch, why not?
Philip Orleans
On Sun, Aug 28, 2022, 3:22 PM John Passaro wrote:
> interfacing with an external tool absolutely seems like the correct answer
> to me. a fact worth m
Sounds great to me. I also use Bash for mission-critical processes.
Philip
On Mon, Jul 4, 2022 at 8:22 AM Yair Lenga wrote:
>
> Hi,
>
> In my projects, I'm using bash to manage large scale jobs. Works very well,
> especially, when access to servers is limited to ssh. One annoying issue is
> the e
On Fri, 2021-11-12 at 19:48 +0100, Andreas Schwab wrote:
> FILE1 -nt FILE2 True if file1 is newer than file2 (according to
>modification date).
>
> Andreas.
>
So now we have a relation for 'older than' and for 'newer than', but how about
'oldest' (executable), and
On Wed, 2021-11-17 at 14:06 +0200, Ilkka Virta wrote:
> On Wed, Nov 17, 2021 at 1:33 PM Andreas Schwab wrote:
> > On Nov 17 2021, Michael J. Baars wrote:
> >
> >
> >
> > > When -N stands for NEW, and touch (-am) gives you a new file
> >
> >
>
On Fri, 2021-11-12 at 19:48 +0100, Andreas Schwab wrote:
> FILE1 -nt FILE2 True if file1 is newer than file2 (according to
>modification date).
>
> Andreas.
>
This would indeed also solve the problem at hand :)
On Mon, 2021-11-15 at 09:23 -0500, Chet Ramey wrote:
> On 11/12/21 4:36 AM, Mischa Baars wrote:
>
> > Could you please restore the Fedora 32 behaviour? Someone must have read
> > the bash manual a little too precise, because now the statement only
> > returns true when a 'touch -a test' is given a
Yeeh, that's funny indeed :)
Now this:
time ( test2Y=$(stat -c %Y test2); for (( i=0; i<1024; i++ )); do if (( $(stat
-c %Y test1) < ${test2Y} )); then echo >> /dev/null; else echo >> /dev/null; fi;
done; );
real0m4.503s
user0m1.048s
sys 0m3.240s
time ( for (( i=0; i<1024; i++ ));
Am 2021-08-17 um 16:36 schrieb Chet Ramey:
On 8/17/21 8:03 AM, Osipov, Michael (LDA IT PLM) wrote:
Folks,
my compiler (aCC) tells me:
/opt/aCC/bin/aCC -Ae -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"ia64"'
-DCONF_OSTYPE='"hpux11.31"&#x
Am 2021-08-17 um 15:53 schrieb Greg Wooledge:
> On Tue, Aug 17, 2021 at 01:02:06PM +0200, Osipov, Michael (LDA IT
PLM) wrote:
>> this is basically the same issue as I reported in readline:
>>
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.gnu.org%2Farchi
$(GCC:+..} and not $(GCC+..}. I have changed ./configure
locally and it works with /bin/sh.
I assume that this should also work on any other POSIX compliant shell.
Michael
[1]
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
f int sh_builtin_func_t PARAMS((WORD_LIST *)); /* sh_wlist_func_t */
^
"general.h", line 323: error #2020: identifier "WORD_DESC" is undefined
extern int check_identifier PARAMS((WORD_DESC *, int));
^
5 errors detected in the compilation of "siglist.c".
gmake: *** [Makefile:101: siglist.o] Error 2
Weird. I have added #include "command.h" right after chartypes.h in
general.h
Known issue? Platform-specific?
Michael
w.
Note: this pontentionally applies to USE_MKSTEMP/HAVE_MKSTEMP as well.
Michael
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-a6qmCk/bash-5.0=.
-fstack-protector-stron>
uname output: Linux ubuntu 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42
UTC 2
Scraping through this - thanks for the lessons aka explanations.
On 18/03/2021 16:08, Chet Ramey wrote:
On 3/18/21 5:53 AM, Michael Felt wrote:
Yes, something to test. Thx. The ojdk scenario is: /usr/bin/printf >
>(tee -a stdout.log) 2> >(tee -a stderr.log).
So, yes, in thi
On 17/03/2021 23:12, Chet Ramey wrote:
On 3/17/21 3:29 PM, Michael Felt wrote:
I tried as many combinations of commands as I could - and it seems
that the regular behavior of dup2 on the opened fifo is enough to
maintain communication.
It's not, since FIFOs exist in the file system and
27;returns' - it ends via sh_exit() and the end of the routine.
Next time - I'll save all of my debug changes. Got a bit too rigorous
when I cleaned up.
On 17/03/2021 19:03, Chet Ramey wrote:
On 3/17/21 11:52 AM, Michael Felt wrote:
OK - this process on github has not gone exactly as
(pathname);
if (fd < 0)
{
/* Two separate strings for ease of translation. */
On 17/03/2021 16:17, Michael Felt wrote:
On 11/03/2021 18:11, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way.
On 11/03/2021 18:11, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way. An abbreviated (shorter pathnames) example is:
```
bash-5.0$ /usr/bin/printf "Building targets 'product-images
legacy-jre-
On 16/03/2021 16:21, Chet Ramey wrote:
On 3/16/21 11:07 AM, Michael Felt wrote:
On 16/03/2021 14:38, Chet Ramey wrote:
On 3/16/21 8:04 AM, Michael Felt wrote:
Decided to give bash-5.1 a try. I doubt it is major, but I get as
far as:
"../../../src/bash-5.1.0/lib/sh/tmpfile.c", l
On 16/03/2021 14:38, Chet Ramey wrote:
On 3/16/21 8:04 AM, Michael Felt wrote:
Decided to give bash-5.1 a try. I doubt it is major, but I get as far
as:
"../../../src/bash-5.1.0/lib/sh/tmpfile.c", line 289.11: 1506-068 (W)
Operation between types "char*" and "int&q
On 11/03/2021 22:27, Chet Ramey wrote:
On 3/11/21 3:55 PM, Michael Felt (aixtools) wrote:
Sent from my iPhone
On 11 Mar 2021, at 18:15, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way. An
Sent from my iPhone
> On 11 Mar 2021, at 18:15, Chet Ramey wrote:
>
> On 3/11/21 11:28 AM, Michael Felt wrote:
>> Hi,
>> Issue: AdoptOpenJDK build process makes bash calls in a particular way. An
>> abbreviated (shorter pathnames) example is:
>> ```
>&
33868
prw--- 1 aixtools staff 0 Mar 11 08:07
/tmp/sh-np-21233868-1115804781
prw--- 1 aixtools staff 0 Mar 11 08:07
/tmp/sh-np-21233868-3761770506
Getting back to AdoptOpenJDK - a build process has roughly 3750 of these
commands - leaving 7500 files behind i
I vote for this new feature.
On Fri, Jan 22, 2021 at 9:16 AM Chet Ramey wrote:
> On 1/22/21 12:29 AM, William Park wrote:
>
> > But, if data are buried in a mess, then it's very labour-intensive to
> > dig them out. It might be useful to have scanf()-like feature, where
> > stdin or string are
can you point me to your FAQ?
On Mon, Jan 4, 2021 at 8:39 AM Greg Wooledge wrote:
> On Mon, Jan 04, 2021 at 08:26:59AM -0500, Saint Michael wrote:
> > In this case, how do I quickly increase the number stored in "foo"?
> > the file has 1 as content, and I have
In this case, how do I quickly increase the number stored in "foo"?
the file has 1 as content, and I have a new value to add to it quickly.
Is there an atomic way to read,add, write a value to "foo"?
On Mon, Jan 4, 2021 at 8:15 AM Greg Wooledge wrote:
> On Fri, Jan 01, 2021 at 10:02:26PM +0
-level developer. My days coding assembler are long gone.
Philip Orleans
Reference: https://tldp.org/LDP/tlk/ipc/ipc.html
On Sun, Dec 27, 2020 at 12:50 PM Eli Schwartz
wrote:
> On 12/27/20 12:38 PM, Saint Michael wrote:
> > Bash is very powerful for its ability to use all
Bash is very powerful for its ability to use all kinds of commands and pipe
information through them. But there is a single thing that is impossible to
achieve except using files on the hard drive or on /tmp. We need a new
declare -g (global) where a variable would have its contents changed by
subs
I want to suggest a new feature, that may be obvious at this point.
How do I do this?
Philip Orleans
stepwise over a search term, reverting at
each step to a previous value, revert the search position to *its*
correponding, previous value.
--
Michael Allan
Toronto, +1 416 699 9528
http://reluk.ca/
test for AIX. If
not, we can consider this thread 'closed'.
Sincerely,
Michael
On 16/10/2020 15:16, Chet Ramey wrote:
> On 10/16/20 6:31 AM, Michael Felt wrote:
>
>> OK. While - perhaps the root cause is differences in error-codes, or
>> something like that - and not t
10/15/20 3:03 AM, Michael Felt wrote:
>>> Hi.
>>>
>>> I don't actually use bash myself - so something that would be apparent
>>> to a bash user is invisible to me.
>>>
>>> As part of the packaging of bash-5.0.18 (i.e., 5.0 at patch level 18)
On 15/10/2020 16:21, Chet Ramey wrote:
> On 10/15/20 3:03 AM, Michael Felt wrote:
>> Hi.
>>
>> I don't actually use bash myself - so something that would be apparent
>> to a bash user is invisible to me.
>>
>> As part of the packaging of bash-5.0.1
On 15/10/2020 16:11, k...@plushkava.net wrote:
> On 15/10/2020 08:03, Michael Felt wrote:
>
>> $ exec > $ exit
>> root@x065:[/data/prj/gnu/bash/bash-5.0.18]
>>
>> ```
>>
>> As you can see by the return of the original PS1 - the sub-shell
>> (./b
> 2
> $ ulimit -n 6
> $ ulimit -n
> 6
> $ exec $ exit
> root@x065:[/data/prj/gnu/bash/bash-5.0.18]
>
> ```
>
> As you can see by the return of the original PS1 - the sub-shell
> (./bash) 'crashed' -- I did not type 'exit' - that is a result of the
> 'exec
> Hope this helps,
>
> Michael (aka aixtools).
>
>
>
>
Hi.
I don't actually use bash myself - so something that would be apparent
to a bash user is invisible to me.
As part of the packaging of bash-5.0.18 (i.e., 5.0 at patch level 18) I
ran the test suite.
a) is there a flag I can pass so that it ignores the UTF-8 tests? I do
not want to not build U
e:
>
> On 9/30/20 3:12 AM, Michael Green wrote:
>
> > Bash Version: 5.0
> > Patch Level: 17
> > Release Status: release
> >
> > Description:
> >
> > The included short script when run with the following command results
> > in execve "
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
-fstack-protector-strong -grecord-gcc-switches
-specs=/usr/li
Sent from my iPhone
> On 17 Apr 2019, at 01:37, Paul Wise wrote:
>
>> On Tue, 2019-04-16 at 14:57 -0400, Chet Ramey wrote:
>>
>> Why take so much effort to (imperfectly) figure out and display
>> things you already know?
>
> Correctness. If what the user knows
You mean think they know, bett
.c and
I'll add some additional logic to not add to the hash table in this case.
Thanks,
On Fri, Apr 5, 2019 at 11:00 AM Chet Ramey wrote:
> On 4/5/19 2:28 AM, Michael S wrote:
> > Hello,
> >
> > I believe I have found a bug when using the posix compliant bash. From
&g
Hello,
I believe I have found a bug when using the posix compliant bash. From this
page point 53
https://www.gnu.org/software/bash/manual/html_node/Bash-POSIX-Mode.html it
states that type and command should not return a binary that is non
executable. For most cases this is currently true and the
w bugs every single day. I, for
example, am subscribed to the Emacs bugs. There are much more open bug
reports I'd like to see ...
Best regards, Michael.
y several GNU projects use debbugs.gnu.org, which runs
Debian's BTS software.
> Chet
Best regrds, Michael.
Greg Wooledge writes:
> Bash doesn't use a formal bug tracking system. Chet manages it all
> by hand. Your best bet is to find the list archive copy of this thread,
> and bookmark it. (Start at <http://lists.gnu.org/archive/html/bug-bash/>.)
I see, thanks!
Best regards, Michael.
;
> Thanks for the report. Try the attached patch and see if that fixes the
> crash.
Thanks a lot, your patch fixes the problem.
> Chet
Best regards, Michael.
PS: Could you pls give me a bug number or something like this, that I
can reference to?
,
including HISTSIZE=0. The second line, after the "#$ " prompt, starts a
shell function declaration. The third and fourth line belong to this
shell function. After the fourth line, bash dies. The exit code is 139.
The same scenario, but with HISTSIZE=1, works proper.
Best regards, Michael.
> On 11/1/2018 12:43 PM, Michael Felt wrote:
>>> I am mainly surprised by "process file table is full" - is there
>>> something specific I can do to look at this more closely?
>> No, it's expected. That script tests the behavior when the process&#x
> On 10/31/2018 9:31 PM, Chet Ramey wrote:
>> On 10/31/18 3:13 PM, Michael Felt wrote:
>>
>> Running "make test", and I amy have forgotten something I did in the past.
>> a) running tests as root (initially)
>> b) ends with:
>> run-vredir
>&g
> On 10/31/2018 9:24 PM, Chet Ramey wrote:
>> On 10/31/18 3:03 PM, Michael Felt wrote:
>> Hi,
>>
>> I finally got around to patching and packaging bash-4.4.23 and had to
>> run a "make distclean" because I had copied the old version and without
On 10/31/2018 9:03 PM, Michael Felt wrote:
> Hi,
>
> I finally got around to patching and packaging bash-4.4.23 and had to
> run a "make distclean" because I had copied the old version and without
> the make distclean make kept looking for "bashversion"
stall yacc, which is what make is complaining
about now - but I also wonder if I could have avoided this by trying to
build oot (out of tree). Is this supported, or even recommended?
Thanks for a great product!
Michael
"rltty.c", line 398.1: 1506-485 (S) Parameter declaration list is
incompatible with declarator for rltty_warning.
make[1]: *** [Makefile:72: rltty.o] Error 1
make: *** [Makefile:663: lib/readline/libreadline.a] Error 1
/opt/bin/make returned an error
make -i compiles the rest of the files. Obvious
I'll start all over again - using the following structure:
cd dist; wget distro..tar.gz
cd ../src; gzip -dc ../dist/distro.tar.gz | tar xf -
mkdir ../distro; cd ../distro
../src/distro/configure --arguments; make; make distclean
../src/distro/configure --arguments; make
As I have not been bu
I can down the distribution, e.g.
ftp://ftp.gnu.org/gnu/bash/bash-4.4.18.tar.gz, unpack it, goto base
directory and run configure.
Thought I had reported this earlier, but guess not!
If after a successful build, I run "make distclean" - "./configure &&
make" no longer works.
e.g.:
root@x0
k, but
something has changed in newer versions of the shell - the unquoted version
if [ -d ${FOO:=""} ]; then echo yes; else echo no; fi
gives "yes" on 4.2 onwards but "no" on 4.1. Also, replacing := with :-
gives "no" on both versions when unquoted or unqu
c Linux 7 and it happens with the latest
release on both.
This is a simplified version of some code from a Cadence setup script; the
above behaviour causes it to fail on SL7.
Michael Gordon
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
can generate solutions and
also protect our intellectual property. I am not smart enough to write it,
but somebody will.
Yours
Federico
On Mon, Sep 11, 2017 at 2:54 PM, Bob Proulx wrote:
> Saint Michael wrote:
> > Dear Maintainer
>
> Note that I am not the maintainer.
&
Dear Maintainer
Is there a commercial or free software that can take a Bash script and
transparently turn it into a C executable, provided the machines where it
runs has any of the external commands like awk, etc?
Something like a Java virtual machine, for Shell.
I think this language is powerful
Bash has an unusual behaviour when a non-expanding here-document (<<‘EOT’) is
used inside $(…) command substitution. Newline joining occurs within the
document when it would not if the same document were not inside a command
substitution, while other shells do not perform it in either case.
Thi
h", line 47.22: 1506-334 (S) Identifier mbchar_t has
already been defined on line 175 of "../src/bash-4.4/include/shmbchar.h".
make: 1254-004 The error code from the last command is 1.
This is from a build done from the beta release from 24 hours ago.
Michael
On Mon, Oct 26, 2015
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -DPA
Hellol.
I have founded a bug in variable manipulation behavior of bash version
4.2.53.
Constructions ${parameter,pattern} and ${parameter,,pattern} does not
working properly:
michael@kazakov:~> VAR=COLORADO
michael@kazakov:~> echo ${VAR,c}
COLORADO
michael@kazakov:~> echo ${VAR,,o}
I do not mind installing yacc :)
How about the redefine of mbchar_t ?
On Fri, Oct 23, 2015 at 2:45 PM, Chet Ramey wrote:
> On 10/22/15 3:47 PM, aixtools wrote:
>> On 2015-10-15 16:23, Chet Ramey wrote:
>>> The first beta release of bash-4.4 is now available with the URL
>>>
>>> ftp://ftp.cwru.ed
Hi Greg,
thank you for your answer!
> On 16 Jun 2015, at 14:58, Greg Wooledge wrote:
>
> On Tue, Jun 16, 2015 at 01:56:31PM +0200, Michael Le Barbier Grünewald wrote:
>> 1>&2 {
>>printf "$@"
>>printf '\n'
&g
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin14.3.0
Compiler: /usr/bin/clang
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='d\
arwin14.3.0' -DCONF_MACHTYPE='x86_64-apple-darwin14.3.0' -DCONF_VENDOR='apple' \
-DLOCALEDIR
u understand my difficulties and i am glad if someone help
with it.
Best regards,
Michael
I am using patch 2.7.0 - and I get the warnings about dangerous files (what
is a dangerous file I ask myself) - but patching proceeds without any
problems.
Michael
On Thu, Oct 2, 2014 at 11:09 PM, Chet Ramey wrote:
> On 9/30/14, 2:18 PM, Matthew Gessner wrote:
> > I apologize, but
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
Hi!
On 11/28/2013 02:32 PM, Flene TOUMANI wrote:
> Is it possible to get a feedback on the issue? (E.g. a confirmation that this
> is a bug).
Sounds like you've run into this problem (patch available):
http://lists.gnu.org/archive/html/bug-bash/2013-10/msg00114.html
/haubi/
On 11/14/2013 08:56 PM, Chet Ramey wrote:
> On 11/8/13 6:26 PM, John Dawson wrote:
>> The following surprised me. I thought line 4 of the output, and certainly
>> line 5 of the output, should have said "0 /dev/fd/63" too. Is this behavior
>> a bug?
>
> I'm still looking at this. I have not had a
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
When /dev/fd is missing, and named pipes are used instead (like on AIX),
this snippet sometimes does work right, wrong, or hang - depending on
the operating system's process scheduler timing:
for x in {0..9}; do echo $x; done > >(
cnt=0; while read line; do let cnt=cnt+1; done; echo $cnt
)
<>
-- Forwarded message --
From: Eric Blake
Date: Wed, 02 Jan 2013 10:41:07 -0700
Subject: Re: No such file or directory
To: Michael Williamson
On 01/02/2013 10:30 AM, Michael Williamson wrote:
> Hi Eric,
>
> Thanks for your explanation. I realize now that I should
&g
library needed for file or interpreter cannot be
found."?
Thanks,
-Mike
On 1/1/13, Aharon Robbins wrote:
> In article ,
> Michael Williamson wrote:
>>Hi,
>>
>>I have a complaint. Apparently, when unknowingly attempting to run a
>>32-bit executable file
Hi,
I have a complaint. Apparently, when unknowingly attempting to run a
32-bit executable file on a 64-bit computer, bash gives the error message
"No such file or directory". That error message is baffling and frustratingly
unhelpful. Is it possible for bash to provide a better error message
in t
and print out. However after the fork the command executed ("ls") seems to be
unable to access stdin, stdout, stderr and goes into defunct.
Any help or guidance is appreciated, is there somewhere in the source code of
bash that would point me in the right direction?
Thanks
Michael
On 08/28/2012 09:21 AM, Roman Rakus wrote:
> On 08/01/2012 03:13 PM, Chet Ramey wrote:
>> On 7/30/12 10:41 AM, Roman Rakus wrote:
>>
>>> Hmm... I don't know much about boundaries of maximum number of user
>>> processes. But anyway - do you think that (re)changing js.c_childmax (when
>>> `ulimit -u
On 07/29/2012 12:46 AM, Chet Ramey wrote:
> On 7/27/12 9:50 AM, Michael Haubenwallner wrote:
>
>> With attached patch I haven't been able to break the testcase below so far
>> on that AIX 6.1 box here.
>>
>> But still, the other one using the $()-childs still
On 07/26/2012 11:37 PM, Michael Haubenwallner wrote:
> On 07/26/12 20:29, Chet Ramey wrote:
>> OK, we have some data, we have a hypothesis, and we have a way to test it.
>> Let's test it.
>>
>> Michael, please apply the attached patch, disable RECYCLES_PIDS, an
On 07/26/12 20:29, Chet Ramey wrote:
OK, we have some data, we have a hypothesis, and we have a way to test it.
Let's test it.
Michael, please apply the attached patch, disable RECYCLES_PIDS, and run
your tests again. This makes the check for previously-saved exit statuses
uncondit
On 07/25/12 19:06, Chet Ramey wrote:
Well, _SC_CHILD_MAX is documented across platforms as:
Heck, even POSIX specifies CHILD_MAX as:
"Maximum number of simultaneous processes per real user ID."
Also, one Linux machine actually shows the _SC_CHILD_MAX value equal to
kernel.pid_max (32768 here
On 07/25/2012 04:50 PM, Chet Ramey wrote:
>> The AIX 6.1 I've debugged on has:
>> #define CHILD_MAX 128
>> #define _POSIX_CHILD_MAX 25
>> sysconf(_SC_CHILD_MAX) = 1024
> Bash prefers sysconf(_SC_CHILD_MAX) and will use it over the other
> defines (lib/sh/oslib.c:getmaxchild()). I don't kno
On 07/25/2012 03:20 PM, Michael Haubenwallner wrote:
> On 07/25/2012 09:59 AM, Michael Haubenwallner wrote:
>> On 07/25/2012 03:05 AM, Chet Ramey wrote:
>>> Bash holds on to the status of all terminated processes, not just
>>> background ones, and only checks for the
On 07/25/2012 02:14 PM, Greg Wooledge wrote:
> On Wed, Jul 25, 2012 at 09:59:28AM +0200, Michael Haubenwallner wrote:
>> OTOH, AFAICT, as long as a PID isn't waitpid()ed for, it isn't reused by
>> fork().
>> However, I'm unable to find that in the POSIX s
1 - 100 of 186 matches
Mail list logo
