Sponsored Content
Top Forums Shell Programming and Scripting Unable to catch the output after core dump and bus error Post 302364792 by rakeshou on Saturday 24th of October 2009 12:18:44 AM
Old 10-24-2009
Quote:
Originally Posted by binlib
when the program ran alone without redirection or pipe line, the output went to screen which was line buffered so you can see it before it died. All the other scenarios you had later involved buffering of larger amount of data. Due to the sudden death of the program the output was lost.
You can run the program under a tty program or modify the source code to make it line buffered or flush the output.
Would appreciate if you could explain or could lead me to the solution to this problem.

Thank You.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. UNIX for Dummies Questions & Answers

core dump

Hi , Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine. Q is how does one read this core file, or I should say 'what is this core file'? thnx (2 Replies)
Discussion started by: buRst
2 Replies

3. UNIX for Advanced & Expert Users

Bus Error Core Dumped

I faced following problem while restoring root backup Server : Compaq Proliant 6000 OS SCO : Unixware 7.0 #tar - xvf /dev/rmt/ctape1 After extracting some files following error message occurred and process stopped # BUS ERROR CORE DUMPED What may be the problem? How to avoid... (1 Reply)
Discussion started by: j1yant
1 Replies

4. Programming

core dump

how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies

5. Shell Programming and Scripting

Segmentation Fault(Core Dump) Error

Hi all, I have a folder with some 28 files. I have a script file that will iteratively take one file at a time from the folder and provide an output for the input file. Till the 7th file, there was no problem but from the 8th file onwards, i got this Segmentation Fault(Core Dump) error. A file... (2 Replies)
Discussion started by: mick_000
2 Replies

6. UNIX for Dummies Questions & Answers

No core dump

my progrme complaints 'Segmentation fault'. How to let it print 'Segmentation fault(core dumped)' and generate core dump file? $ulimit unlimited (22 Replies)
Discussion started by: vistastar
22 Replies

7. Solaris

ipsec error seen in ikeadm dump p1 output

****** (0 Replies)
Discussion started by: meghnasreddy
0 Replies

8. Programming

Core dump error in code

HI, I am getting run time error when am trying to compile the following coe can any one please help me while (fgets(strLine, MAX_LINELEN, vobjFile) != NULL && feof(vobjFile) == 0) { printf("this is the first loop\n"); while (strcmp(strLine, "BEGINTRANS\n") !=... (5 Replies)
Discussion started by: uday.sena.m
5 Replies

9. UNIX for Dummies Questions & Answers

Get the eeprom dump using PCI bus address

Hi, I need to get an output that is the same as "ethtool -e eth0" But I need to use another method that does not use the eth port ID (ethX). Does anyone know of any method? Thanks!! (3 Replies)
Discussion started by: h0ujun
3 Replies

10. Shell Programming and Scripting

Unable to catch the redirection error when the disk is full

Hi Experts, Problem summary : I am facing the below problem on huge files when the disk is getting full on the half way through the execution. If the disk was already full , the commands fail & everything is fine. Sample Code : head_rec_data_file=`head -1 sample_file.txt` cat... (9 Replies)
Discussion started by: Pruthviraj_shiv
9 Replies
KILL(1) 							Linux User's Manual							   KILL(1)

NAME
kill - send a signal to a process SYNOPSIS
kill [ -signal | -s signal ] pid ... kill [ -L | -V, --version ] kill -l [ signal ] DESCRIPTION
The default signal for kill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP, CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL. Negative PID values may be used to choose whole process groups; see the PGID column in ps command output. A PID of -1 is special; it indicates all processes except the kill process itself and init. SIGNALS
The signals listed below may be available for use with kill. When known constant, numbers and default behavior are shown. Name Num Action Description 0 0 n/a exit code indicates if a signal may be sent ALRM 14 exit HUP 1 exit INT 2 exit KILL 9 exit cannot be blocked PIPE 13 exit POLL exit PROF exit TERM 15 exit USR1 exit USR2 exit VTALRM exit STKFLT exit might not be implemented PWR ignore might exit on some systems WINCH ignore CHLD ignore URG ignore TSTP stop might interact with the shell TTIN stop might interact with the shell TTOU stop might interact with the shell STOP stop cannot be blocked CONT restart continue if stopped, otherwise ignore ABRT 6 core FPE 8 core ILL 4 core QUIT 3 core SEGV 11 core TRAP 5 core SYS core might not be implemented EMT core might not be implemented BUS core core dump might fail XCPU core core dump might fail XFSZ core core dump might fail NOTES
Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill to solve the conflict. EXAMPLES
kill -9 -1 Kill all processes you can kill. kill -l 11 Translate number 11 into a signal name. kill -L List the available signal choices in a nice table. kill 123 543 2341 3453 Send the default signal, SIGTERM, to all those processes. SEE ALSO
pkill(1), skill(1), kill(2), renice(1), nice(1), signal(7), killall(1). STANDARDS
This command meets appropriate standards. The -L flag is Linux-specific. AUTHOR
Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one might also work correctly. Please send bug reports to <procps-feedback@lists.sf.net> Linux November 21, 1999 KILL(1)
All times are GMT -4. The time now is 01:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy