- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: HP IA64- Getting runtime error "SEGV_MAPERR - ...
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
тАО04-24-2008 02:42 AM
тАО04-24-2008 02:42 AM
HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
I am porting HP UX 32 to 64 bit platform.When run the application it core dumped.
Below mentioed is the stack trace.
#0 0xc000000009c3da40:0 in MTPQty::operator= (this=0x600000000cf50f60,
inQty=@0x9fffffffffffda30) at mtpqty.cpp:68
#1 0xc00000000879fc90:0 in GeneralCapacity_sdb::SetParcelSize (
this=0x600000000019f2a0, irow=2, pUseCap=0x600000000039d020,
ParcelQty=@0x600000000004ff90) at capacity_sdb.cpp:278
#2 0xc0000000087972a0:0 in GeneralCapacity_sdb::query (
this=0x600000000019f2a0, pQtyConstraint=0x600000000004ff30,
pParcelSize=0x600000000004ff80, withLock=false) at capacity_sdb.cpp:130
#3 0xc000000008796c60:0 in GeneralCapacity_sdb::query (
this=0x600000000019f2a0, withLock=false) at capacity_sdb.cpp:29
#4 0xc000000008798760:0 in GeneralCapacity_sdb::query (
this=0x600000000019f2a0, rFilter=@0x9fffffffffffdc20)
at capacity_sdb.cpp:65
#5 0xc000000008a82730:0 in Config_db::query (this=0x600000000019f230,
rFilter=@0x9fffffffffffdc20, bFromAgents=true) at trconfig_db.cpp:39
#6 0xc000000006cce660:0 in DSAStaticSet::queryConfig (this=0x9fffffffbf6bfbb0)
at dsastaticset.cpp:1239
#7 0xc000000006dcccd0:0 in AllAgent::queryConfig (this=0x60000000002b8340)
at allagent.cpp:218
#8 0xc000000006e24250:0 in AutoRetenderAgent::initialize (
this=0x60000000002b8340, pEvent=0x600000000005b400)
at autoretenderagent.cpp:85
#9 0xc000000006e29540:0 in AutoRetenderAgent::allAction (
---Type
this=0x60000000002b8340, pEvent=0x600000000005b400)
at autoretenderagent.cpp:364
#10 0x400000000000d070:0 in ProcessArmEvents () at arm_main.cpp:483
#11 0x4000000000008670:0 in main (argc=5, argv=0x9fffffffffffe568)
at arm_main.cpp:210
- Tags:
- SIGSEGV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2008 03:34 AM
тАО04-24-2008 03:34 AM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
If you want to debug at the machine level, provide:
(gdb) disas $pc-16*8 $pc+16*4
(gdb) info reg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2008 12:04 AM
тАО04-25-2008 12:04 AM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
In inQty=@0x9fffffffffffda30, What is the significance of the @ prefix in the address ? Does it mean its an invalid address ?
I am not understanding the assembly language code
;;; File: mtpqty.cpp
;;; 68 Qty::operator=(inQty);
0x9fffffffbb2609c0:0 <:operator>:
mov r33=r37;;
0x9fffffffbb2609c0:1 <:operator>:
mov r41=r32
0x9fffffffbb2609c0:2 <:operator>:
mov r42=r33
0x9fffffffbb2609d0:0 <:operator>:
nop.m 0x0
0x9fffffffbb2609d0:1 <:operator>:
nop.m 0x0
0x9fffffffbb2609d0:2 <:operator>:
br.call.dptk.few b0=0x9fffffffbb25ec30;;
0x9fffffffbb2609e0:0 <:operator>:
mov r1=r38
0x9fffffffbb2609e0:1 <:operator>:
nop.m 0x0
0x9fffffffbb2609e0:2 <:operator>:
br.cond.dptk.few MTPQty::operator=(Qty const&)+144;;
0x9fffffffbb2609f0:0 <:operator>:
nop.m 0x0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2008 02:47 AM
тАО04-25-2008 02:47 AM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
Then you need to debug why they are bad.
>In inQty=@0x9fffffffffffda30, what is the significance of the @ prefix in the address?
It just means that inQty is AT that address.
>I am not understanding the assembly language code
I would tell you what it means. You were suppose to supply:
(gdb) disas $pc-16*8 $pc+16*4
(gdb) info reg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2008 03:39 AM
тАО04-25-2008 03:39 AM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
In between I am analyzing the data corruption of inQty and let you know the findings.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2008 07:07 PM
тАО04-25-2008 07:07 PM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
The code has:
0x9fffffffbb260a20:0 adds r10=8,r32
0x9fffffffbb260a20:1 adds r11=8,r33
0x9fffffffbb260a30:1 ld8 r11=[r11]
0x9fffffffbb260a40:0 st8 [r10]=r11;; <<<<<
This is code that is copying the 2nd and 3rd words from inQty to this. It is aborting trying to store to "this".
(gdb) p *this
Error accessing memory address 0x600000000cf50f70: Bad address.
Which shows the same problem, a bad "this" pointer.
>In between I am analyzing the data corruption of inQty and let you know the findings.
Ok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2008 10:05 PM
тАО05-05-2008 10:05 PM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
However, after correcting this data problem, I found the below issue.
aCC runtime: Uncaught exception of type "os_time_toolkit_error". (rethrow)
Abort(coredump)
I check the stack trace,
#0 0xc000000000322cf0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
(gdb) where
#0 0xc000000000322cf0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
#1 0xc000000000247c90:0 in raise+0x30 () from /usr/lib/hpux64/libc.so.1
#2 0xc0000000002e56b0:0 in abort+0x190 () from /usr/lib/hpux64/libc.so.1
#3 0xc00000000178dcf0:0 in std::terminate()+0x50 ()
from /usr/lib/hpux64/libCsup.so.1
#4 0xc0000000017b34d0:0 in __cxa_rethrow+0x90 ()
from /usr/lib/hpux64/libCsup.so.1
#5 0x400000000000d820:0 in ProcessArmEvents () at arm_main.cpp:540
#6 0x4000000000008670:0 in main (argc=5, argv=0x9fffffffffffe588)
at arm_main.cpp:211
Could you please analyze ?
- Tags:
- throw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2008 02:33 AM
тАО05-06-2008 02:33 AM
Re: HP IA64- Getting runtime error "SEGV_MAPERR - Address not mapped to object"
aCC runtime: Uncaught exception of type "os_time_toolkit_error". (rethrow)
#3 0xc00000000178dcf0:0 in std::terminate()+0x50 libCsup.so.1
#4 0xc0000000017b34d0:0 in __cxa_rethrow+0x90
#5 0x400000000000d820:0 in ProcessArmEvents arm_main.cpp:540
#6 0x4000000000008670:0 in main
arm_main.cpp:211
>Could you please analyze?
There is nothing to analyze, everything is there in the first error message I added.
You are rethrowing os_time_toolkit_error and there is no catch handler to catch it in ProcessArmEvents or main.
If you want to trace the original throw, you can use these gdb commands:
(gdb) catch catch
(gdb) catch throw
- Tags:
- exception