Sponsored Content
Top Forums Programming Why do I receive Program received signal SIGABRT, Aborted? Post 302634727 by Corona688 on Thursday 3rd of May 2012 06:03:34 PM
Old 05-03-2012
Quote:
Originally Posted by Errigour
Thanks neutronscott. While you still have the program handy could you maybe help me with an overflow problem. When I receive with my two functions create_character, and character_login. Well when I receive data that is longer then recv is receiving It seems to recv again three or four times depending on the amount of characters over the limit there are.
It's like a file. If you read 30 bytes from a 100 byte file, there's still 90 bytes to go. If you don't know how long it is, you have to keep reading until you find the end.

Except it's a file that arrives whenever it feels like it, in chunks of whatever variable size it feels like. If you don't know how long a field's supposed to be, the socket can't tell you. Not dependably, anyway. It might arrive in the size it was sent in -- or the socket might decide to wait and send it all in one big 64K chunk. You can't guess.

Your protocol should include some sort of terminator for variable-length things, since you can't guess from how much you read.
 

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
recv(2) 							System Calls Manual							   recv(2)

Name
       recv, recvfrom, recvmsg - receive a message from a socket

Syntax
       #include <sys/types.h>
       #include <sys/socket.h>

       cc = recv(s, buf, len, flags)
       int cc, s;
       char *buf;
       int len, flags;

       cc = recvfrom(s, buf, len, flags, from, fromlen)
       int cc, s;
       char *buf;
       int len, flags;
       struct sockaddr *from;
       int *fromlen;

       cc = recvmsg(s, msg, flags)
       int cc, s;
       struct msghdr msg[];
       int flags;

Description
       The and system calls are used to receive messages from a socket.

       The call can be used only on a connected socket. The and calls can be used to receive data on a socket, whether or not it is in a connected
       state.  For further information, see

       If from is nonzero, the source address of the message is filled in.  The fromlen is a value-result parameter, initialized to  the  size	of
       the buffer associated with from, and modified on return to indicate the actual size of the address stored there.  The length of the message
       is returned in If a message is too long to fit in the supplied buffer, excess bytes can be discarded, depending on the type of  socket  the
       message is received from.  For further information, see

       If  no  messages  are  available  at  the socket, the receive call waits for a message to arrive, unless the socket is nonblocking.  If the
       socket is nonblocking, a of -1 is returned, and the external variable errno is set to EWOULDBLOCK.  For further information, see

       The call can be used to determine when more data arrives.

       The flags argument to a send call is formed by ORing one or more of the values following values:
       #define	 MSG_OOB   0x1	/* process out-of-band data */
       #define	 MSG_PEEK  0x2	/* peek at incoming message */
       The call uses a msghdr structure to minimize the number of directly supplied parameters.  This structure has the following form, as defined
       in <sys/socket.h>:
       struct msghdr {
	      caddr_t  msg_name;	/* optional address */
	      int      msg_namelen;	/* size of address */
	      struct   iov *msg_iov;	/* scatter/gather array */
	      int      msg_iovlen;	/* # elements in msg_iov */
	      caddr_t  msg_accrights;	/* access rights sent/received */
	      int      msg_accrightslen;
       };
       Here,  msg_name and msg_namelen specify the destination address if the socket is unconnected; msg_name can be given as a null pointer if no
       names are desired or required.  The msg_iov and msg_iovlen describe the scatter gather locations, as described in Access rights to be  sent
       along with the message are specified in msg_accrights , which has length msg_accrightslen .

Return Values
       These calls return the number of bytes received, or -1 if an error occurred.

Diagnostics
       The call fails under the following conditions:

       [EBADF]	      The argument s is an invalid descriptor.

       [EINVAL]       The argument length of the message is less than 0.

       [EMSGSIZE]     The message sent on the socket was larger than the internal message buffer.

       [ENOTCONN]     A call was made to from an unconnected stream socket.

       [ENOTSOCK]     The argument s is not a socket.

       [EWOULDBLOCK]  The socket is marked nonblocking and the receive operation would block.

       [EINTR]	      The receive was interrupted by delivery of a signal before any data was available for the receive.

       [EFAULT]       The  data  was  specified  to  be  received  into a nonexistent or protected part of the process address space. The argument
		      fromlen points outside the process address space.

See Also
       read(2), send(2), socket(2)

																	   recv(2)
All times are GMT -4. The time now is 04:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy