![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| bus error (coredump) | charu | UNIX for Dummies Questions & Answers | 4 | 12-12-2007 06:05 AM |
| coredump after every reboot | xnightcrawl | UNIX for Advanced & Expert Users | 2 | 03-24-2006 06:41 PM |
| Bus error(coredump | Student37 | UNIX for Dummies Questions & Answers | 3 | 07-01-2005 03:53 PM |
| Strncpy - coredump | vijaysabari | High Level Programming | 0 | 06-30-2004 10:55 AM |
| coredump | lala | High Level Programming | 2 | 03-12-2002 09:26 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
handling a coredump on HP?
This works for all my normal executions. But on one machine, a coredump is expected on one command. We don't care and know it will always happen, but need to confirm the version info from the start of the output. This is output from the exe:
$ ./Up -*-*- XXXXXXX UPDATE XXXXX Version nnnnnnnn -*-*- -*-*- Copyright (C) 1998-2007 xxxxxxxxxxxxxx, Inc. -*-*- Processing begins: 10/4/2007 10:48:12 Tracking Database Connect Error Memory fault(coredump) However, when I send the output to a file, the output file is empty: $ ./Up > ../Up_output.txt 2>&1 Memory fault(coredump) $ cd .. $ cat Up_output.txt $ How do I capture the output so I can check the version and continue processing? |
|
||||
|
The core file has program version info as well.
Code:
file /path/to/core And. No way should an app 'be expected' to dump core in production. If someone has deliberately written code that forces itself to core dump for debug reasons, okay. But that's development. Never production. |
|
||||
|
Quote:
Did you mean an app running in production to be cent percent perfect all the time ? I accept that bugs that dump core in production are not a welcoming feature. But I believe neither of the code that is written could be ever said 100% bug free, so core dumps in production are more like a way of life and they are bound to happen. I didn't mean to say anything negatively and only point I would like to stress is " it happens " ( I know its a lame excuse and hate that myself very much ) |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|