exception handling Post: 52364

Sponsored Content

Top Forums UNIX for Advanced & Expert Users exception handling Post 52364 by jim mcnamara on Wednesday 16th of June 2004 05:29:03 PM

06-16-2004

Registered User

Not exactly. The NT family of OSes throw exceptions which are handled by an exception vector. You can throw exceptions -- in the sense of software error trapping in Unix -- using C++ as well. It's no different from MSVC++ in that regard.

Unix creates signals - think of them as exactly like software interrupts -- to handle exceptions. This is not like the Windows message pump.

These signals are sent to a process, which then has a signal handler. It's like an exception vector (table) except that it's a single function that processes signals or lets them through.

On a Unix box, type "man signal" and it will explain a little bit about signal processing.

Here is a site with PDF's that go into some depth (it's for linux, which for signals, is just fine):

www.advancedlinuxprogramming.com

It's a whole book. You're gonna need it. If you're going to non-Linux, try Richard Stevens book 'Advanced Programming in the UNIX Environment'.

Good Luck---

The thing that's going to kill you is that NT(XP) was built from the ground up on threading. Unix was not.

pthreads are supported just fine in most Unix versions, and work well.

jim mcnamara

View Public Profile for jim mcnamara

Find all posts by jim mcnamara

9 More Discussions You Might Find Interesting

1. Programming

Linux g++ 2.95.3 exception handling

Anybody happen to be familiar with any deficiencies with g++ 2.95.3 regarding exception handling, specifically in multi-threaded / multi-module (shared library) based applications? I'm seeing behavior where thrown exceptions are not caught, but basically ignored causing the application to...

2. Shell Programming and Scripting

Exception-handling in Shell programs

Hi all, I am writing a set of scripts and some of these are nested within others. I want to be able to execute a single high-level script at the command-line, which in turn may invoke other scripts as required, and when a failure occurs in any of the nested scripts, I want to be able to track...

3. Linux

Handling "command not found" exception

hello friends, I am given a project to handle the command not found exception.I am using RED HAT 9. Generally, when we press a wrong command in the terminal: example :- " $cet " in place of " $cat ". Then we get this exception. But I need to give the output as the combinations that are possible...

4. Shell Programming and Scripting

Exception Handling

Hi, I have written a script to load csv files into a mysql database, however, i would like for the shell script to exit in the event of an error (missing file, load error etc.) - currently if an error is encountered the next statement is processed - This is how i am loading the csv scripts ...

5. Programming

Advanced Exception Handling in C++

Hi Friend, Could you please provide me with some tutorial for Advanced Exception handling in C++, mainly set_terminate() and set_unexpected() functions? Please find the details below: OS: Unix Compiler: gcc. Thanks. :) Awesome001

6. Shell Programming and Scripting

Exception handling

Sometimes when I try to use curl to upload to an ftp server, I get the message: $curl -T file.wmv ftp.eu.filesonic.com --user user:password curl: (8) Got a 421 ftp-server response when 220 was expected How do I get the script to try again if I get the message curl: (8)?

7. Programming

Exception Handling C++

Hello All, I have a question ....which I am totally confused about! If I have a fxn foo in a program which returns a logical value. But it has a posssiblity to throw some exception. Now my exception handler returns a value as a string stating why the exception occured. But my...

8. Solaris

solaris 7 exception

Hi all, An application works well under 2.6 but under 7 it gives TEXT_IO exceptions. (Is_Open, Check_Is_Open, Get_Line procedures). Any idea? Regards

9. Shell Programming and Scripting

Monitor logs for exception and if exception come then sent an email

Hi Folks, please advise , I have logs generated on unix machine at location /ops/opt/aaa/bvg.log , now sometimes there come exception in these logs also, so I want to write such a script such that it should continuously monitor these logs and whenever any exception comes that is it try to find...

LEARN ABOUT XFREE86

kill

KILL(1)                                                            User Commands                                                           KILL(1)

NAME

       kill - send a signal to a process

SYNOPSIS

       kill [options] <pid> [...]

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 or -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.

OPTIONS

       <pid> [...]
              Send signal to every <pid> listed.

       -<signal>
       -s <signal>
       --signal <signal>
              Specify the signal to be sent.  The signal can be specified by using name or number.  The behavior of signals is explained  in  sig-
              nal(7) manual page.

       -l, --list [signal]
              List signal names.  This option has optional argument, which will convert signal number to signal name, or other way round.

       -L, --table
              List signal names in a nice table.

       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

       kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7), skill(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.

REPORTING BUGS

       Please send bug reports to <procps@freelists.org>

procps-ng                                                          October 2011                                                            KILL(1)