How to debug signals

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) How to debug signals
# 1  
Old 04-21-2009
How to debug signals

Hi,
In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point.
I am working on Mac X and using XCode.

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help with trap and signals

I am having issues with trap not working inside a script. I am currently trying this on a Knoppix system V 5.1. What I would like to happen is when I press control c, a message gets echoed and the script is ended. For example: #! /bin/bash trap "echo CTRL c was pressed ; break" SIGINT... (11 Replies)
Discussion started by: Basherrr
11 Replies

2. UNIX for Advanced & Expert Users

Help with Signals

Hi All, The problem statement is as below: Problem: A process (exe) is getting executed in background. The output of this process is getting logged in a file. After successfully running for some time the process gets terminated. In the log file following is present: ^M[7m Interrupt ^M[27m... (8 Replies)
Discussion started by: Praty.27
8 Replies

3. UNIX for Dummies Questions & Answers

pending signals

I was wondering about following. If I have set of 3 signals. And they are all blocked.Now at some point in the program the set is unblocked. Which signal will be delivered first.This is my set....SIGTSTP,SIGQUIT,SIGINT.When I added them in the set and unblock them I did it in following order... ... (1 Reply)
Discussion started by: joker40
1 Replies

4. UNIX for Dummies Questions & Answers

Blocking signals

I know how to add signal to a set. But what if I want to add 2 or 3 signals to the set. I know I can use sigaddset (&set,SIGBUS)....but what if I want to add SIGBUS and SIGALRM at once. Do i have to do it like this.. sigaddset (&set,SIGBUS); sigaddset (&set,SIGALRM); Is there another way to... (0 Replies)
Discussion started by: joker40
0 Replies

5. UNIX for Dummies Questions & Answers

perror with signals

I have following problem with this code.. First time trough the main loop..... perror gives ....blocked signal:success(all other times gives illlegal seek) Should every time trought the main loop be success?? And the perror otside of main loop...didn't change mask:success That line of code... (2 Replies)
Discussion started by: joker40
2 Replies

6. UNIX for Dummies Questions & Answers

Help understanding signals

I am having trouble with folowing sigset_t s; // now s represents set of signals sigemptyset(&s) ; // initialize this set and exclude all the signals from it.is it empty? sigaddset(&s,SIGILL);//this set containts only SIGILL signal sigprocmask(SIG_BLOCK,&s,NULL);//lost on this one Can... (3 Replies)
Discussion started by: joker40
3 Replies

7. Programming

Can we debug Signals

Hi, In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point. I am working on Mac X and using XCode. Thanks (1 Reply)
Discussion started by: Saurabh78
1 Replies

8. Programming

Using Signals

How can use signals in a C program If i want a child program to signal it's parent program that it(child) program has completed the task that it was assigned.:confused: (2 Replies)
Discussion started by: kapilv
2 Replies

9. UNIX for Dummies Questions & Answers

Signals...

(posted this in the scripting forum as well, but figured it should go here) So, what's going on is this: For our program, we had to create our own shell, and if the user pressed ctrl-c just at the cmdline, then this signal would be ignored, but if there is a foreground process running, let's... (0 Replies)
Discussion started by: blind melon
0 Replies

10. Programming

Signals In HP-UX

does the way of handling, interrupting signals in HP-UX same as that of solaris. If there is difference than what it is.?:confused: (1 Reply)
Discussion started by: kapilv
1 Replies
Login or Register to Ask a Question
openapp(1)						       GNUstep System Manual							openapp(1)

NAME
openapp - launch applications from the command line SYNOPSIS
openapp [--find] [--debug [--gdb= debuger]] [ --library-combo=library-combo ] application [arguments...] DESCRIPTION
The openapp command allows you to launch graphical GNUstep applications from the command line. application is the complete or relative name of the application program with or without the .app extension, like Ink.app. arguments are the arguments passed to the application. openapp first checks whether the application is in the current working directory. If not then searches the GNUstep domains' Applications folders in the following order: User (i.e. ~/GNUstep/Applications), Local, Network, System. First match wins. OPTIONS
--find application will print out the full path of the application executable which would be executed, without actually executing it. It will also list all paths that are attempted. --debug application starts the application in the debugger. By default gdb, but this can be changed with the --gdb= argument or through the GDB shell variable. --library-combo=library-combo Starts the application with the specified library combo. This is a rarely used option in a non-flattened setup. See the library- combo(7) man-page for more information about the different library combinations. --help print above usage description. EXAMPLES
Start Ink.app without additional parameters: openapp Ink.app Launch Ink.app and pass it the --debug argument: openapp --debug Ink.app To determine which executable is launched by openapp, type: openapp --find Ink.app The output of the above command might be something like: /usr/GNUstep/Local/Applications/Ink.app/Ink ENVIRONMENT
GNUSTEP_CONFIG_FILE is used to determine where the GNUstep.sh configuration file is located. If the variable is not set openapp tries to locate it in the folder where openapp was started, then in the user domain, and as a last resort in the system domain (or actually the place you configured (--with-config-file=) during building). GDB Sets the debugger to use when --debug is used. SEE ALSO
debugapp(1), GNUstep(7), gopen(1), library-combo(7), opentool(1) HISTORY
Work on openapp started October 1997. openapp was originally written by Ovidiu Predescu <ovidiu@net-community.com> and is now maintained by Nicola Pero <nicola.pero@meta-innova- tion.com> AUTHORS
This manual page was first written July 2003 by Martin Brecher <martin@mb-itconsulting.com>. Updated with notes from Hubert Chathi <uhoreg@debian.org> and Dennis Leeuw <dleeuw@made-it.com>, December 2007 by Dennis Leeuw. gnustep-make 12/12/2007 openapp(1)