- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: PA Risk Executable on Itanium Server
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
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
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
тАО06-26-2008 06:24 AM
тАО06-26-2008 06:24 AM
Re: PA Risk Executable on Itanium Server
>Note that the parameters are changed.
Did you try this thing ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 07:07 AM
тАО06-26-2008 07:07 AM
Re: PA Risk Executable on Itanium Server
>Sri: Try to find out: how you end up calling fnc_mbStrLen("") from fnc_StrLen("\n").
>Note that the parameters are changed.
I can't debug at that level (I don't know how, I am calling a 3rd party library and program crashes)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 10:36 AM
тАО06-26-2008 10:36 AM
Re: PA Risk Executable on Itanium Server
Just to confirm, is fnc_InitDgn your code or its also in some third party library? which third party library?
May be I am confused by the naming convention used.
From where did you get the third party libraries with debugging symbols?
PS: Every answer does not deserve 10 points
http://forums11.itrc.hp.com/service/forums/helptips.do?#28
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 11:07 AM
тАО06-26-2008 11:07 AM
Re: PA Risk Executable on Itanium Server
I compiled the code on PA with -g option and debugged it on Itanium using wdb and from that session I am getting all the info you see here.
In any case, looks like no one really surprised by the fact that the exec runs fine through debugger but crashes when run by itself! ( I have seen similar behaviour with some VB code but never understood why)
Tks
Rao
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 11:30 AM
тАО06-26-2008 11:30 AM
Re: PA Risk Executable on Itanium Server
Its very strange that the 3rd party is giving you libs with full debugging symbols. Not many vendors do this(never seen this for any HP library). Are you intentionally using debug version of the third party libs?
anyway, If you know who own this lib and have a support contract; you can involve them to look into this. You can show them the stack and provide them the core file.
as a call to fnc_mbStrLen("") from fnc_StrLen("\n") seems fishy to me \, I am wondering why would somebody do that?
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 11:36 AM
тАО06-26-2008 11:36 AM
Re: PA Risk Executable on Itanium Server
Dennis has already provided a couple of possible reasons:
"I've had a few cases where it runs in the debugger. The obvious cases are uninitialized variables.
I've seen other cases where the debugger's private mapping of shlibs causes readonly strings to be writable and then it won't abort. But that should fail on PA too. "
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 11:59 AM
тАО06-26-2008 11:59 AM
Re: PA Risk Executable on Itanium Server
Also, going back to checking the other Itanium server (where this exec runs without failing), I found that linker, libc and Aries are at a later(higher) patch level on my system.
I have increased the maxdsiz_64bit to 6GB, still got the error.
Are there any other kernel parameters I should check?
-Tks
Rao
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 10:16 PM - edited тАО09-11-2011 07:14 AM
тАО06-26-2008 10:16 PM - edited тАО09-11-2011 07:14 AM
Re: PA-RISC Executable on Integrity server
>I don't have source multibyte.c, may be it is part of the 3rd party libraries I am using.
You can use "info module $pc" to find out which shlib.
>I am attaching the gdb and elfdump output.
Thanks, that says your problem isn't in fnc_mbStrChr at all! You may need a newer PA64 gdb to tell you that.
You are aborting here: pcoqh: c000000008054c98
This shows you are on the first ldd of an import stub. R27/DP is bad:
0xc000000008054c98 <.stub>: ldd -0x2068(%dp),%r1
0xc000000008054c9c <.stub+4>: bve (%r1)
0xc000000008054ca0 <.stub+8>: ldd -0x2060(%dp),%dp
dp: 9fffffffdfeffa10
Does this value show up in the "info shared" list under the dlt column?
You should also try "info module $dp".
This seems to be in this shlib:
CoreMMF 0000000000071ad8 9fffffffdfedf000 0000000000021000 0000000000021000
dp - 0x2068 == 9fffffffdfefd9a8, is still in that shlib.
>Srikrishan: as a call to fnc_mbStrLen("") from fnc_StrLen("\n") seems fishy to me
It's not, gdb is lying to you.
>Aries are at a later (higher) patch level on my system.
Do you have the latest? If not try that. Otherwise try removing the Aries patch you have and install the other one that works.
>I have increased the maxdsiz_64bit to 6GB, still got the error.
>Are there any other kernel parameters I should check?
There is nothing wrong with maxdsiz_64bit. You are using a trivial amount of data:
CoreLoad 0000000000000ad8 8000000100000000 0000000000009000 0000000000009000
CoreStck 0000000000009ad8 9fffffffe0000000 0000000000020000 0000000000020000
Plus the shlibs in CoreMMF.
- « Previous
- Next »