- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- failure in writing the signal context
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-08-2009 02:43 AM
тАО04-08-2009 02:43 AM
failure in writing the signal context
Apr 8 12:36:45 bgbmap01 vmunix: Pid 6975 was killed due to failure in writing the signal context.
Apr 8 12:49:08 bgbmap01 vmunix: Pid 2985 was killed due to failure in writing the signal context.
Apr 8 12:50:03 bgbmap01 vmunix: Pid 2065 was killed due to failure in writing the signal context.
Apr 8 13:00:26 bgbmap01 vmunix: Pid 3672 was killed due to failure in writing the signal context.
Apr 8 13:03:23 bgbmap01 vmunix: Pid 5280 was killed due to failure in writing the signal context.
Apr 8 13:05:00 bgbmap01 vmunix: Pid 23421 was killed due to failure in writing the signal context.
Apr 8 13:05:04 bgbmap01 vmunix: Pid 6280 was killed due to failure in writing the signal context.
Apr 8 13:05:23 bgbmap01 vmunix: Pid 10249 was killed due to failure in writing the signal context.
Apr 8 13:05:26 bgbmap01 vmunix: Pid 6469 was killed due to failure in writing the signal context.
Apr 8 13:05:30 bgbmap01 vmunix: Pid 15596 was killed due to failure in writing the signal context.
Apr 8 13:05:38 bgbmap01 vmunix: Pid 3222 was killed due to failure in writing the signal context.
Apr 8 13:05:41 bgbmap01 vmunix: Pid 12735 was killed due to failure in writing the signal context.
Apr 8 13:05:45 bgbmap01 vmunix: Pid 6085 was killed due to failure in writing the signal context.
Apr 8 13:06:28 bgbmap01 vmunix: Pid 16019 was killed due to failure in writing the signal context.
Apr 8 13:06:30 bgbmap01 vmunix: Pid 15313 was killed due to failure in writing the signal context.
- Tags:
- stack overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2009 03:01 AM
тАО04-08-2009 03:01 AM
Re: failure in writing the signal context
Unless you know which were those PIDs or find corefiles, this is useless.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2009 01:41 AM
тАО04-09-2009 01:41 AM
Re: failure in writing the signal context
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2009 01:58 AM
тАО04-09-2009 01:58 AM
Re: failure in writing the signal context
You have to find the core file of this issue, { check the date of the core } after you could analyse the core for example by
file core
what core
strings -a core
to see what could be the cause of the creation. When you have the program, check for patch or tuning of the stack
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2009 08:19 PM
тАО04-09-2009 08:19 PM
Re: failure in writing the signal context
These are typically useless. You need to use a debugger to get a stack trace to start:
gdb executable core
(gdb) bt