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

Hi Chet, there've been follow-up discussions and reviews here with our linker folks (see [1] for some details on the bug that was open to capture those) and consensus is that best approach is to not compile with bash's own malloc routines. Indeed, ld(1)'s -z interpose option is a rather big h

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 refer

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

following-up on 3rd item: [..] 3. What does the traceback look like when bash is run under gdb and allowed to fail? I suspect that the libraries are pre-bound to use the system's malloc, and the calls to different malloc libraries are causing the core dumps. Another possibility is that

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

On 10/ 6/08 05:11 PM, Chet Ramey wrote: 2. What library installs the `sigacthandler'? It's not a function in bash. It is a symbol in libc, but there's no indication which library installs it as a signal handler. I have just tried psig on on running bash (in another config), and see

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 cha