Sponsored Content
Top Forums Programming Why do I receive Program received signal SIGABRT, Aborted? Post 302634039 by Errigour on Wednesday 2nd of May 2012 08:57:28 PM
Old 05-02-2012
Ouput:
Code:
CYGWIN_NT-5.1 a 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin

I wanna provide some information about this that might help. It seems to happen when a funtions recv function returns 0 to the while loop below. I might be wrong though but it just seems that way to me.
Code:
        while(keepsake != NULL)
        {
            if(FD_ISSET(keepsake->newfd, &read_fds))
            {
                if(keepsake->state == CHARACTER_LOGIN)      /* Character login    */
                    character_login(keepsake);
                else if(keepsake->state==CREATE_CHARACTER)  /* Character creation */
                    create_character(keepsake);
            }
            keepsake = keepsake->next;
        }

 

10 More Discussions You Might Find Interesting

1. IP Networking

Tcp Ip Send Receive Server Program

Requirements: A server program should read a file and send the message to the client . if the file is not there, then switch to the receive part of the same program and receive any messages from the socket. If no messages to receive then switch to send part of the program to... (2 Replies)
Discussion started by: Rajeshsu
2 Replies

2. Programming

Program received signal SIGABRT, Aborted.

I ran degugger in C++ and the followings are the message I got: Program received signal SIGABRT, Aborted. 0x002a57a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 (gdb) info s #0 0x002a57a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x002e97f5 in raise () from /lib/tls/libc.so.6... (1 Reply)
Discussion started by: napapanbkk
1 Replies

3. Programming

Program received signal SIGSEGV, Segmentation fault.

Dear all, I used debugger from C++ and these are the message I got: Program received signal SIGSEGV, Segmentation fault. 0x00323fc0 in free () from /lib/tls/libc.so.6 (gdb) info s #0 0x00323fc0 in free () from /lib/tls/libc.so.6 #1 0x00794fa1 in operator delete () from... (5 Replies)
Discussion started by: napapanbkk
5 Replies

4. Shell Programming and Scripting

Writing a program to receive the GPS data and send to other server

Hi, I would like to write a program to receive the GPS data and then send the data via network to other program. All of the program is not write yet(include host and sender) All of the server OS is unix or linux Could you mind to give me some idea to do this? Thanks so much! Ken ... (2 Replies)
Discussion started by: kenlok
2 Replies

5. AIX

Received signal #11, SIGSEGV [default] on AIX 6.1

Hello, One of our customer is getting segmentation fault when he runs his shell script which invokes our executable on AIX 6.1. On AIX 5.3, there were no issues. Here is the truss output. 811242: __loadx(0x0A040000, 0xF0D3A26C, 0x00000000, 0x00000009, 0x00000000) = 0xF026E884... (0 Replies)
Discussion started by: erra_krishna
0 Replies

6. AIX

nim: error signal number 2 received

Hi to all, i am trying to make mksysb backup of a NIM client machine from NIM master and while i am reading that the backup is done successfully i get an error message below and it doesnt exit the smit screen. also the status of the command appears to be running. is there anybody who knows why... (3 Replies)
Discussion started by: omonoiatis9
3 Replies

7. Programming

Program received signal: “EXC_BAD_ACCESS”?

I am making a command line program in C using XCode. When running the program, it initially does what it is supposed to do (asks me for a file path). However, when I type in a valid and existing file path, it gives me the following error: Program received signal: “EXC_BAD_ACCESS”.... (6 Replies)
Discussion started by: mdonova33
6 Replies

8. Programming

Please help:program hang stuck there signal handling on POSIX Message Queue UNIX C programming

in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario: client:Knock Knock server:who's there client: Eric Server:Eric,Welcome. client:exit all process terminated ... (1 Reply)
Discussion started by: ouou
1 Replies

9. Solaris

backup aborted

hi all I am getting following error while taking backup using the command ufsdump 0ubf 512 /dev/rmt/0cbn /database/backup2/rman_backup/level0 >> /database/backup2/backup_tape/level0_rman_06sep12 2>&1; from the log i got the error bash# tail -f level0_rman_06sep12 DUMP: Date of... (3 Replies)
Discussion started by: nikhil kasar
3 Replies

10. Programming

Free() - Program getting aborted.

I am trying to learn C and while trying out some code, the program is getting aborted while I am calling free(). Here is the code: #include <stdlib.h> #include <stdio.h> void print_by_ptr(char **str) { printf("<%s>\n",*str); printf("Now I am modifying the str.\n"); *str =... (3 Replies)
Discussion started by: chacko193
3 Replies
Globus Callback Signal Handling(3)				   globus common				Globus Callback Signal Handling(3)

NAME
Globus Callback Signal Handling - Macros #define GLOBUS_SIGNAL_INTERRUPT Functions globus_result_t globus_callback_space_register_signal_handler (int signum, globus_bool_t persist, globus_callback_func_t callback_func, void *callback_user_arg, globus_callback_space_t space) globus_result_t globus_callback_unregister_signal_handler (int signum, globus_callback_func_t unregister_callback, void *unreg_arg) void globus_callback_add_wakeup_handler (void(*wakeup)(void *), void *user_arg) Detailed Description Macro Definition Documentation #define GLOBUS_SIGNAL_INTERRUPT Use this to trap interrupts (SIGINT on unix). In the future, this will also map to handle ctrl-C on win32. Function Documentation globus_result_t globus_callback_space_register_signal_handler (intsignum, globus_bool_tpersist, globus_callback_func_tcallback_func, void *callback_user_arg, globus_callback_space_tspace) Fire a callback when the specified signal is received. Note that there is a tiny delay between the time this call returns and the signal is actually handled by this library. It is likely that, if the signal was received the instant the call returned, it will be lost (this is normally not an issue, since you would call this in your startup code anyway) Parameters: signum The signal to receive. The following signals are not allowed: SIGKILL, SIGSEGV, SIGABRT, SIGBUS, SIGFPE, SIGILL, SIGIOT, SIGPIPE, SIGEMT, SIGSYS, SIGTRAP, SIGSTOP, SIGCONT, and SIGWAITING persist If GLOBUS_TRUE, keep this callback registered for multiple signals. If GLOBUS_FALSE, the signal handler will automatically be unregistered once the signal has been received. callback_func the user func to call when a signal is received callback_user_arg user arg that will be passed to callback space the space to deliver callbacks to. Returns: o GLOBUS_CALLBACK_ERROR_INVALID_SPACE o GLOBUS_CALLBACK_ERROR_INVALID_ARGUMENT o GLOBUS_SUCCESS otherwise globus_result_t globus_callback_unregister_signal_handler (intsignum, globus_callback_func_tunregister_callback, void *unreg_arg) Unregister a signal handling callback. Parameters: signum The signal to unregister. unregister_callback the function to call when the callback has been canceled and there are no running instances of it (may be NULL). This will be delivered to the same space used in the register call. unreg_arg user arg that will be passed to callback Returns: o GLOBUS_CALLBACK_ERROR_INVALID_ARGUMENT if this signal was registered with persist == false, then there is a race between a signal actually being caught and therefor automatically unregistered and the attempt to manually unregister it. If that race occurs, you will receive this error just as you would for any signal not registered. o GLOBUS_SUCCESS otherwise void globus_callback_add_wakeup_handler (void(*)(void *)wakeup, void *user_arg) Register a wakeup handler with callback library. This is really only needed in non-threaded builds, but for cross builds should be used everywhere that a callback may sleep for an extended period of time. An example use is for an io poller that sleeps indefinitely on select(). If the callback library receives a signal that it needs to deliver asap, it will call the wakeup handler(s), These wakeup handlers must run as though they were called from a signal handler (don't use any thread utilities). The io poll example will likely write a single byte to a pipe that select() is monitoring. This handler will not be unregistered until the callback library is deactivated (via common). Parameters: wakeup function to call when callback library needs you to return asap from any blocked callbacks. user_arg user data that will be passed along in the wakeup handler Author Generated automatically by Doxygen for globus common from the source code. Version 14.7 Tue Nov 27 2012 Globus Callback Signal Handling(3)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy