- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: using operator= on value field of type std::st...
Operating System - HP-UX
1753317
Members
5200
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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-08-2009 06:54 PM
тАО06-08-2009 06:54 PM
Re: using operator= on value field of type std::string of std::map causes segmentation fault
>see attached the gdb commands results.
Your thread stack usage is too small for stack overflow:
p $sp - $sp_save >>= 11104
You seem to have a null pointer where you are trying to change the color of a parent of a parent node to RED:
0xc000000018d64a00:2 <_C_insert+0xb02>: adds r8=8,r56;; parent
0xc000000018d64a10:0 <_C_insert+0xb10>: ld8 r55=[r8];;
0xc000000018d64a10:1 <_C_insert+0xb11>: mov r8=r55
0xc000000018d64a10:2 <_C_insert+0xb12>: mov r9=1;; BLACK
0xc000000018d64a20:0 <_C_insert+0xb20>: st4 [r8]=r9
0xc000000018d64a20:1 <_C_insert+0xb21>: mov r54=r39;;
0xc000000018d64a20:2 <_C_insert+0xb22>: adds r8=8,r54;; parent
0xc000000018d64a30:0 <_C_insert+0xb30>: ld8 r53=[r8]
0xc000000018d64a30:2 <_C_insert+0xb32>: adds r8=8,r53;; parent
0xc000000018d64a40:0 <_C_insert+0xb40>: ld8 r52=[r8]
0xc000000018d64a40:2 <_C_insert+0xb42>: mov r8=r52;; NULL
0xc000000018d64a50:0 <_C_insert+0xb50>: st4 [r8]=r0 << RED
Somehow your rbtree has been corrupted.
I assume you know that multiple threads can't be accessing the map if one is modifying it?
Your thread stack usage is too small for stack overflow:
p $sp - $sp_save >>= 11104
You seem to have a null pointer where you are trying to change the color of a parent of a parent node to RED:
0xc000000018d64a00:2 <_C_insert+0xb02>: adds r8=8,r56;; parent
0xc000000018d64a10:0 <_C_insert+0xb10>: ld8 r55=[r8];;
0xc000000018d64a10:1 <_C_insert+0xb11>: mov r8=r55
0xc000000018d64a10:2 <_C_insert+0xb12>: mov r9=1;; BLACK
0xc000000018d64a20:0 <_C_insert+0xb20>: st4 [r8]=r9
0xc000000018d64a20:1 <_C_insert+0xb21>: mov r54=r39;;
0xc000000018d64a20:2 <_C_insert+0xb22>: adds r8=8,r54;; parent
0xc000000018d64a30:0 <_C_insert+0xb30>: ld8 r53=[r8]
0xc000000018d64a30:2 <_C_insert+0xb32>: adds r8=8,r53;; parent
0xc000000018d64a40:0 <_C_insert+0xb40>: ld8 r52=[r8]
0xc000000018d64a40:2 <_C_insert+0xb42>: mov r8=r52;; NULL
0xc000000018d64a50:0 <_C_insert+0xb50>: st4 [r8]=r0 << RED
Somehow your rbtree has been corrupted.
I assume you know that multiple threads can't be accessing the map if one is modifying it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2009 10:25 PM
тАО06-08-2009 10:25 PM
Re: using operator= on value field of type std::string of std::map causes segmentation fault
hi,
tanx a lot. i reviewed the many lines of code and i think there is a shared memory access problem. it's still not confirmed 100% but some maps and other objects that crashes occurred when accessing them seem to not be protected.
i have to say that the same code / process runs on Solaris without crashing. of course if the code is not safe it needs to be fixed, but maybe Solaris "Tolerates" this not safe code better.
BTW how RU converting (or know the meaning) the stack prints to the words: parent, BLACK, RED, NULL, '<', etc... ?
BR,
Amit.
tanx a lot. i reviewed the many lines of code and i think there is a shared memory access problem. it's still not confirmed 100% but some maps and other objects that crashes occurred when accessing them seem to not be protected.
i have to say that the same code / process runs on Solaris without crashing. of course if the code is not safe it needs to be fixed, but maybe Solaris "Tolerates" this not safe code better.
BTW how RU converting (or know the meaning) the stack prints to the words: parent, BLACK, RED, NULL, '<', etc... ?
BR,
Amit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2009 03:23 AM
тАО06-09-2009 03:23 AM
Re: using operator= on value field of type std::string of std::map causes segmentation fault
>how are you converting (or know the meaning) the stack prints to the words: parent, BLACK, RED, NULL, etc...?
I look at the assembly and match it up to the source. The abort location is in the ip or $pc register.
I look at the assembly and match it up to the source. The abort location is in the ip or $pc register.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP