Sponsored Content
Top Forums Shell Programming and Scripting Unable to catch the output after core dump and bus error Post 302367051 by arlensen on Saturday 31st of October 2009 06:08:06 PM
Old 10-31-2009
Question

can you try
Code:
db2bfd -b test.bnd > output.log 2>&1

this should enable you to both catch standard and error output
 

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
Printexc(3)							   OCaml library						       Printexc(3)

NAME
Printexc - Facilities for printing exceptions. Module Module Printexc Documentation Module Printexc : sig end Facilities for printing exceptions. val to_string : exn -> string Printexc.to_string e returns a string representation of the exception e . val print : ('a -> 'b) -> 'a -> 'b Printexc.print fn x applies fn to x and returns the result. If the evaluation of fn x raises any exception, the name of the exception is printed on standard error output, and the exception is raised again. The typical use is to catch and report exceptions that escape a func- tion application. val catch : ('a -> 'b) -> 'a -> 'b Printexc.catch fn x is similar to Printexc.print , but aborts the program with exit code 2 after printing the uncaught exception. This function is deprecated: the runtime system is now able to print uncaught exceptions as precisely as Printexc.catch does. Moreover, calling Printexc.catch makes it harder to track the location of the exception using the debugger or the stack backtrace facility. So, do not use Printexc.catch in new code. val print_backtrace : Pervasives.out_channel -> unit Printexc.print_backtrace oc prints an exception backtrace on the output channel oc . The backtrace lists the program locations where the most-recently raised exception was raised and where it was propagated through function calls. Since 3.11.0 val get_backtrace : unit -> string Printexc.get_backtrace () returns a string containing the same exception backtrace that Printexc.print_backtrace would print. Since 3.11.0 val record_backtrace : bool -> unit Printexc.record_backtrace b turns recording of exception backtraces on (if b = true ) or off (if b = false ). Initially, backtraces are not recorded, unless the b flag is given to the program through the OCAMLRUNPARAM variable. Since 3.11.0 val backtrace_status : unit -> bool Printexc.backtrace_status() returns true if exception backtraces are currently recorded, false if not. Since 3.11.0 val register_printer : (exn -> string option) -> unit Printexc.register_printer fn registers fn as an exception printer. The printer should return None or raise an exception if it does not know how to convert the passed exception, and Some s with s the resulting string if it can convert the passed exception. Exceptions raised by the printer are ignored. When converting an exception into a string, the printers will be invoked in the reverse order of their registrations, until a printer returns a Some s value (if no such printer exists, the runtime will use a generic printer). When using this mechanism, one should be aware that an exception backtrace is attached to the thread that saw it raised, rather than to the exception itself. Practically, it means that the code related to fn should not use the backtrace if it has itself raised an exception before. Since 3.11.2 OCamldoc 2014-06-09 Printexc(3)
All times are GMT -4. The time now is 05:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy