Operating System - Linux
1752799 Members
6046 Online
108789 Solutions
New Discussion юеВ

ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

 
SOLVED
Go to solution
GnanaShekar
Regular Advisor

ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Hi,

We need to run PARISC version of bash shell on one of our HP Unix Itanium servers.

The details of our HP Unix Itanium server is

# uname -a
HP-UX bgpcia2 B.11.23 U ia64 0946427944 unlimited-user license

We have installed the PARISC version of bash and its PARISC dependencies (gettext, libgcc, libiconv & termcap).

---------------------------------
# swlist | grep -ie bash -ie gettext -ie libiconv -ie libgcc -ie termcap
bash 3.2 bash
gettext 0.16 gettext
libgcc 4.1.1 libgcc
libiconv 1.11 libiconv
termcap 1.3.1 termcap

# file /usr/bin/bash
/usr/bin/bash: PA-RISC2.0 shared executable dynamically linked
# file file /usr/local/bin/gettext
file: cannot open
/usr/local/bin/gettext: PA-RISC2.0 shared executable dynamically linked -not stripped
# file /usr/local/lib/libstdc++.sl
/usr/local/lib/libstdc++.sl: PA-RISC1.1 shared library
# file usr/local/bin/iconv
usr/local/bin/iconv: PA-RISC2.0 shared executable dynamically linked
# file /usr/local/lib/libiconv.sl
/usr/local/lib/libiconv.sl: PA-RISC2.0 shared library -not stripped
# file /usr/local/lib/libtermcap.sl
/usr/local/lib/libtermcap.sl: PA-RISC2.0 shared library
---------------------------------

I have assigned the PARISC bash shell for an user who requires it as the default shell. He has no problem with login in and working with the bash shell

However while he is executing commands on this server remotely (from an linux server) he is getting the below error:

---------------------------------
ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash
---------------------------------

Find below the details we could get from running the gdb (GNU debugger) on the HP Unix Itanium server:

---------------------------------
-bash-3.2$ gdb bash core.bash
HP gdb 5.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Detected PA executable.
Invoking /usr/ccs/bin/gdbpa.
Use "run" to continue execution.
(no debugging symbols found)...(gdb) run
Starting program: /usr/bin/bash
Aries ERROR:[pid=22891] Application makes TTRACE syscall without setting environ ment variable PA_DEBUG=1. Further emulation not possible.

-bash-3.2$ export PA_DEBUG=1

-bash-3.2$ gdb bash core.bash
HP gdb 5.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Detected PA executable.
Invoking /usr/ccs/bin/gdbpa.
Use "run" to continue execution.
(no debugging symbols found)...(gdb) run
Starting program: /usr/bin/bash
warning: Unable to find _DLD_HOOK symbol in object file.
warning: Suggest linking with /opt/langtools/lib/end.o.
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
---------------------------------

Request you to suggest in this matter.

Thanks & Regards,







 

 

P.S. This thread has been moved from HP-UX > System Administration to HP-UX > languages - HP Forums Moderator

11 REPLIES 11
Dennis Handly
Acclaimed Contributor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Why do you need to run the PA version? Why not use an IPF version?

Was there a signal number mentioned anywhere?

>Use "run" to continue execution.

Why did you use run? You need to use bt. I assume you are trying to debug bash??
GnanaShekar
Regular Advisor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Hi,

We need PARISC version of bash, and some other appliations because an application named "autonomy" works only with those.

Also find attached the outcome of "bt" with gdb.

-bash-3.2$ which gdb
/opt/langtools/bin/gdb
-bash-3.2$ file /opt/langtools/bin/gdb
/opt/langtools/bin/gdb: ELF-32 executable object file - IA64
-bash-3.2$ pwd
/home/si_admin
-bash-3.2$ gdb bash core.bash
HP gdb 5.0 for HP Itanium (32 or 64 bit) and target HP-UX 11.2x.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..
Detected PA executable.
Invoking /usr/ccs/bin/gdbpa.
Use "run" to continue execution.
(no debugging symbols found)...(gdb) bt
No stack.
(gdb)

Please suggest,
Thanks & Regards,
Dennis Handly
Acclaimed Contributor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

>We need PARISC version of bash, and some other appliations because an application named "autonomy" works only with those.

I don't see why it cares whether the shell is native or not. But whatever.

Somehow the corefile isn't being passed from the IPF gdb to the PA gdb. (I have no problems on my system. And I get the gdb version after the "Detected PA executable" message.)

Try absolute paths:
$ PA_DEBUG=1 /usr/ccs/bin/gdbpa /usr/bin/bash /home/si_admin/core.bash

You may want to install the latest PA gdb (for IPF) patch: PHSS_34417
GnanaShekar
Regular Advisor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Hi,

Thanks for your reply.

-bash-3.2$ export PA_DEBUG=1
-bash-3.2$ /usr/ccs/bin/gdbpa /usr/bin/bash /home/si_admin/core.bash
HP gdb 3.4 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 3.4 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for warranty/support.
..(no debugging symbols found)...
Core was generated by `bash'.
Program terminated with signal 11, Segmentation fault.
(no debugging symbols found)...
warning: Can't find file -bash referenced in dld_list.


warning: Can't find file referenced in dld_list.

"/opt/sybase/OCS-12_5/bin/": can't read symbols: File format not recognized.
#0 0xc1ad8bbc in ?? ()
(gdb) bt
#0 0xc1ad8bbc in ?? ()
warning: Attempting to unwind past bad PC 0xc1ad8bbc
#1 0xc1b1451c in ?? ()
#2 0xc1b1451c in ?? ()
(gdb)

Dennis Handly
Acclaimed Contributor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

>Core was generated by `bash'.
Program terminated with signal 11, Segmentation fault.

Well at least it tells you the right signal and is looking at the corefile.

>warning: Can't find file -bash referenced in dld_list.

This isn't good. Try installing PHSS_34417.
If this doesn't help, it is possible bash has corrupted the dld data structures and that's why gdb is having problems??
GnanaShekar
Regular Advisor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Hi Dennis,

Thanks for your reply.

Let me explain to you in more detail as to what made us go for bash(PARISC) on HPUnix Itanium server.

We have a PARISC application named "autonomy" that requires "libiconv"(PARISC) library. "autonomy" is not available for IA64, so we have run this on HP Unix Itanium server.

without knowing that the existing bash(IA64) depends on libiconv(IA64), we replaced it with libiconv(PARISC).

Now the user whose default shell was bash could not login. He was thrown out immediately he tried to login.

So we uninstalled the bash(IA64) along with all its IA64 depndencies (gettext, libiconv, termcap & libgcc) & installed bash(PARISC) along with all its PARISC dependenices.

Now we get to see bash core dumping during some occasions.

I have a query though:
1. Can we install both libiconv(PARISC) and libiconv(IA64) and make the bash(IA64) use the libiconv(IA64) and "autonomy" use the libiconv(PARISC)? if so how?

Please suggest,
Thanks & Regards,
Dennis Handly
Acclaimed Contributor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

>1. Can we install both libiconv(PA-RISC) and libiconv(IA64) and make the bash(IA64) use the libiconv(IA64) and "autonomy" use the libiconv(PA-RISC)? if so how?

Sure, by putting the libs in different paths. By convention PA libs should go directly in lib/. IPF libs should go into lib/hpux32/ or lib/hpux64/. Also, IPF libs should have .so instead of .sl.

GnanaShekar
Regular Advisor

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

Hi Dennis,

Thanks.

I have installed both PARISC and IA64 versions of libiconv. However, the swlist command shows only one instance:

# file /usr/local/lib/libiconv.sl
/usr/local/lib/libiconv.sl: PA-RISC2.0 shared library -not stripped

# cd /usr/local/lib
# cd hpux32
# ls -l libiconv*
-rw-r--r-- 1 root sys 1263128 Dec 4 20:33 libiconv.a
-rwxr-xr-x 1 root sys 772 Dec 4 20:33 libiconv.la
-r-xr-xr-x 1 root sys 1058992 Dec 4 20:33 libiconv.so

# file libiconv.so
libiconv.so: ELF-32 shared object file - IA64

# swlist | grep -ie libiconv
libiconv 1.11 libiconv


Also is there a way to list the dynamic dependencies of a PARISC application on HPIA64.

bash-3.2# file pdfslave.exe
pdfslave.exe: PA-RISC2.0 shared executable dynamically linked

bash-3.2# ldd pdfslave.exe
ldd: Invalid file type: "pdfslave.exe". Shared executable or shared library expected.


Please suggest,
Thanks & Regards,
Dennis Handly
Acclaimed Contributor
Solution

Re: ARIES32: Core file for PA32 application saved to /home/si_admin/core.bash

>the swlist command shows only one instance:

Then either you didn't install it with swinstall. Or it was packaged such that the PA version overwrote the IPF version in the IPD.

>Also is there a way to list the dynamic dependencies of a PA-RISC application on HPIA64.

$ SDKROOT=/usr/ccs/pa chatr pdfslave.exe

Using ldd above doesn't give errors but there is no output. The above variable allows you do use other PA linker tools, ar(1), strip(1), odump(1).