Re: [mapfile]: problem reentrance with normal file

Ok, maybe one day we can do it ... Thanks for your clarifications Regards, Serge. Le lun. 12 nov. 2018 à 19:09, Chet Ramey a écrit : > On 11/12/18 12:47 PM, Didou Serge wrote: > > But not work under linux... > > It's probably the difference between using pipes a

Re: [mapfile]: problem reentrance with normal file

But not work under linux... Le lun. 12 nov. 2018 à 17:00, Didou Serge a écrit : > I tested with another configuration and ALL work fine: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: cygwin > Compiler: gcc > Compilation

Re: [mapfile]: problem reentrance with normal file

mat-security uname output: CYGWIN_NT-6.1 EB-5CG63201SJ 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin Machine Type: x86_64-unknown-cygwin Bash Version: 4.4 Patch Level: 12 Release Status: release Le lun. 12 nov. 2018 à 16:48, Didou Serge a écrit : > Ok, in this case, this should not work

Re: [mapfile]: problem reentrance with normal file

Ok, in this case, this should not work either: mapfile -C xx -c 1 UU < <( echo -e "Premiere ligne" A{1..45} "\nDeuxieme ligne" B{1..45} "\nTroisieme ligne" C{1..45}) But, this form work fine. Le lun. 12 nov. 2018 à 15:44, Chet Ramey a écrit : >

[mapfile]: problem reentrance with normal file

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

write() not retried after EINTR in printf and echo

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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/opt/bash-4.4.12

Re: **/ directory wildcards leak file descriptors and memory

On Sat, 23 Jun 2012, Chet Ramey wrote: > On 6/20/12 2:50 PM, Serge van den Boom wrote: > > Bash Version: 4.2 > > Patch Level: 29 > > Release Status: release > > > > Description: > > If you interrupt the evaluation of **/ wildcard expansion, the file >

**/ directory wildcards leak file descriptors and memory

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/opt/bash-4.2/share/locale' -DPA

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Hi Chet, Serge Dussud wrote: On 12/ 8/08 03:00 PM, Chet Ramey wrote: Serge Dussud wrote: Indeed, ld(1)'s -z interpose option is a rather big hammer, as it establishes that the application can interpose on *all* of the symbols that it offers, rather than just the few related to m

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

On 12/ 8/08 03:00 PM, Chet Ramey wrote: Serge Dussud wrote: Indeed, ld(1)'s -z interpose option is a rather big hammer, as it establishes that the application can interpose on *all* of the symbols that it offers, rather than just the few related to malloc. That might be a problem if

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

rom the system ? or, otherwise said, what do bash lose when it's compiled with option --without-bash-malloc ? TIA, Serge [1] http://bugs.opensolaris.org/view_bug.do?bug_id=6778453 On 10/30/08 08:26 PM, Chet Ramey wrote: ah OK, so I guess I need to work on a customized patched for 3.2 then.

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

ok, thanks ! Serge On 10/30/08 08:26 PM, Chet Ramey wrote: ah OK, so I guess I need to work on a customized patched for 3.2 then. Any ideas yet of what the exact change will be in configure.bin so that I can apply to same in our deliveries ? *** ../bash-3.2-patched/configure.in2007-12

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: -z interpose . Could it be the explanation and a possible solution ? Well, let's try it. OK, great. Shall I under

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: -z interpose . Could it be the explanation and a possible solution ? Well, let's try it. OK, great. Shall I understand that you're going to make a patch for this, or is there something else ? Serge Chet

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Hi Chet, any follow-up on this ? tia, Serge [..] From man page ld(1) (snv_99 box): -B direct | nodirect These options govern direct binding. -B direct estab- lishes direct binding information by recording the rela- tionship between each symbol

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

that interposition takes place regardless of the order in which objects are loaded. Explicit interposition also ensures that the runtime linker searches for symbols in any explicit interposers when direct bindings are in effect. . Could it be

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

rc.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/threads/sigaction.c#283 I am not very familiar with this part of Solaris code to be honest. Serge Chet

Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Hi Chet, thanks for the quick answer. More in-line: On 10/ 3/08 10:52 PM, Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: Hello bug-bash, please find attached a bashbug report. I am not sure how to follow-up then, could you advise ? This is the appropriate venue for these reports

bash cores if nscd disabled on Solaris LDAP sasl/gssapi client

Hello bug-bash, please find attached a bashbug report. I am not sure how to follow-up then, could you advise ? Thanks, Serge From: root To: bug-bash@gnu.org Subject: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client Configuration Information [Automatically generated, do not

Re: Bash Commander: new project

tes of binary code added to bash. The commander layer lies somewhere in between the core shell and readline library. Right now I use bashc as a replacement of /bin/bash on my home Mac mini. ___ Serge

Bash Commander: new project

Hello all, What do you think about extending bash functionality with visual two-panel file browser? Here is a new project to implement this: http://bashc.wiki.sourceforge.net/ Critique and suggestions are welcome. ___ Best wishes, Serge

Vertical tab on commandline in UTF-8 mode crashes bash.

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: freebsd5.5 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='freebsd5.5' -DCONF_MACHTYPE='i386-unknown-freebsd5.5' -DCONF_VENDOR='unknown' -DLOCALEDIR='/home/svdb/bashtemp

Re: Question about Xterm title

On Thu, Feb 17, 2005 at 04:12:49PM +0100, Al Elgert wrote: > Hello, > > you can change the title with this command (if the term supports it): > > echo -en "\033]0;--- $HOSTNAME $TERM $$ ---\007" >^^ May be I'm don't explained clearly enough.

Question about Xterm title

badly need this feature. I haven't found any clues in documentation of bash how to achieve this. May be I missed something? Thank you! -- Sincerely yours, Serge ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash