- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: hpux B.11.31 core crash but not in B.11.23
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 02:16 AM
11-24-2008 02:16 AM
hpux B.11.31 core crash but not in B.11.23
we compiling the application on :
HP-UX B.11.23 U ia64 with aCC HP C/aC++ B3910B A.06.15 linked with STLport 5.10
and when we run the application on B.11.23 machine , every thing is working great
but when we move the application to B.11.31
we get core that say :
1 0x4000000000aabe30:0 in stlp_std::basic_string
how can we test what is the problem ?
- Tags:
- STLPort
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 03:03 AM
11-24-2008 03:03 AM
Re: hpux B.11.31 core crash but not in B.11.23
Install and use the gdb debugger for HP-UX 11.31 and analyze the core file.
use tusc to analyze the process as running if possible.
tusc is a system utility for hp-ux that mimics the functionality of strace on Linux.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 07:10 AM
11-24-2008 07:10 AM
Re: hpux B.11.31 core crash but not in B.11.23
we didn't found any thing except the problem with the :
#1 0x4000000000aabe30:0 in stlp_std::basic_string
now we compiled the application on hpux 31 and
and run the application on hpux31 in our local server and its running great but when we move to different hpux 31
we still we getting this error .
what else we can try and find in the machine configuration that can impact ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 07:42 AM
11-24-2008 07:42 AM
Re: hpux B.11.31 core crash but not in B.11.23
#0 0x4000000003057620:0 in __milli_memmove+0x80 ()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 11:45 AM
11-24-2008 11:45 AM
Re: hpux B.11.31 core crash but not in B.11.23
but when we move the application to B.11.31
11.31 should be forward compatible. If it fails it means your application is illegal and may have some uninitialized variables, or some problems with different inputs.
1 0x4000000000aabe30:0 stlp_std::basic_string
>how can we test what is the problem?
By printing out the variables that are used there. (Have you compiled with -g0?)
Or by looking at the machine code with:
(gdb) frame 1
(gdb) print *this
(gdb) disas 0x4000000000aabe30-16*20 0x4000000000aabe30+16*4
(gdb) info reg
Are you in a thread? You could have a thread stack overflow.
>we didn't found anything except the problem with the:
But did you look at the statement in question and look at all the variables?
>what else we can try and find in the machine configuration that can impact?
What does your application do? Does it look at your machine configuration?
>I'm getting this error in gdb:
#0 0x4000000003057620:0 __milli_memmove+0x80
This is a user error. You have bad addresses or a length in your call to memcpy or memmove.
What does this show?
(gdb) p /x $r32
(gdb) p /x $r33
(gdb) p /x $r34
Does it match what you see in frame 1?
- Tags:
- pthread
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2008 10:56 PM
11-24-2008 10:56 PM
Re: hpux B.11.31 core crash but not in B.11.23
>Are you in a thread? You could have a thread stack overflow.
well i don't know .. how can i check this ?
>But did you look at the statement in question and look at all the variables?
yes we set all variables.
>What does your application do? Does it look at your machine configuration?
the application reads and process text files
in multi threaded mode. it does not read machine configuration just it local application configuration
just reminder we have the same machine
with the same configuration ( as we know .. )
and the application works fine .
im attaching the output of the gdb command in text file i do not know how to analyze it.
can you please take a quick look at it .
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 12:49 AM
11-25-2008 12:49 AM
Re: hpux B.11.31 core crash but not in B.11.23
with the same configuration ( as we know .. )
and the application works fine .
So have you compared the pathc level and product levels of the 2 systems?
If they're on the same network then:
sysdiff
will do a quick comparison for you.
Otherwise an "swlist -l product" output from both systems run through diff should show any differences.
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 12:56 AM
11-25-2008 12:56 AM
Re: hpux B.11.31 core crash but not in B.11.23
Provide the full stack trace.
>yes we set all variables.
Do they all have valid values? You need to print the contents of the string.
>reads and process text files in multi-threaded mode.
You might want to explain that? No more than one thread per file?
>I'm attaching the output of the gdb command
You need to redo this:
(gdb) bt
(gdb) frame 0
(gdb) disas $pc-16*20 $pc+16*4
(gdb) info reg
It appears you have a null pointer as a target. Relink your application with -z.
- Tags:
- -z
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 03:35 AM
11-25-2008 03:35 AM
Re: hpux B.11.31 core crash but not in B.11.23
well i cant do sysdiff because the second hp
in different place not related to our network×¥
also swlist -l product is problem because i have no root privileges but i emailed to the sysadmin and i hope i will have the diff shortly
about the questions:
>Do they all have valid values? You need to print the contents of the string.
which variable to print ? there is attached stack trace can you please point me where ?
>You might want to explain that? No more than one thread per file?
no its balk of files per thread
>Provide the full stack trace.
attached
>You need to redo this:
>(gdb) bt
>(gdb) frame 0
>(gdb) disas $pc-16*20 $pc+16*4
>(gdb) info reg
also in the attached file
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2008 03:54 AM
11-25-2008 03:54 AM
Re: hpux B.11.31 core crash but not in B.11.23
the test1 is the problematic machine
on the left.
thanks