01-15-2005
No buffer space available
Hi Neo,
Thank you much for your response. You were right about the full buffer space (mbufs) might have been caused by using the calls to "malloc()" or "calloc()" without freeing ("free()") the allocated memory.
However, in this case, the pointer to a structure has been created (without using malloc() or calloc()) at the beginning of an infinite for(;
loop.
I now have a specific question about these two socket errors:
1. socket error 10055 (No buffer space available)
2. socket error 183 (?)
How do I fix the problems to resolve these two socket errors?
Thanks a lot.
DP
10 More Discussions You Might Find Interesting
1. Linux
What does that mean?
traviata being my distant host?
What am i to do? (0 Replies)
Discussion started by: penguin-friend
0 Replies
2. Shell Programming and Scripting
Hi
I am trying to develop a script so that whenever used % reaches 90% it will send an alert mail. Following is the script whic I am tryiing to implement but it show some error.
code:
#! /bin/ksh
df -v | grep -i "/opt" | awk '{print $6}' > space
if ]
then
echo "ALERT YOUR SPACE IS TOO... (6 Replies)
Discussion started by: pankajkrmishra
6 Replies
3. Shell Programming and Scripting
Hi,
I need to check if the value returned by this query is bigger then 20000.
It's not working!
I think that the problem is that the return is with white spaces. How to solve this?
Tks,
Paulo Portugal.
#######################
RESPOSTA=`/oracle/app/product/10.2/bin/sqlplus -s <<EOF
/ as... (2 Replies)
Discussion started by: paulofp
2 Replies
4. Programming
Hello,
I am having trouble clearing the serial port buffer using the iclear and iflush commands. The code runs without errors being returned, but when I check the buffer again there is still data.
The only way I have so far is to read until there is nothing left in the buffer. Shouldn't one... (1 Reply)
Discussion started by: sammy-e
1 Replies
5. Shell Programming and Scripting
Hi
I just want to clean up the space in UNIX. Is there any special command that does this process or do I need to manually type the following
rm <filename>
Any help would be really appreciated. Thanks (2 Replies)
Discussion started by: bobby1015
2 Replies
6. HP-UX
Hi,
How can i clear the command. Suppose using esc k i retrieved teh command, but for some reason I want to clear and type fresh one... how can i do that.
thx (2 Replies)
Discussion started by: bang_dba
2 Replies
7. AIX
I'm running a ksh script that requires user interaction, and said users (myself among them) may get a little trigger happy and get ahead of ourselves and accidentally key in the wrong responses to future prompts in the script.
Naturally, I'd like to prevent that, so how does one clear that... (0 Replies)
Discussion started by: Michael Mullig
0 Replies
8. Solaris
:)Hi Solaris Experts,
I am wondering whether it is possible to clear a network socket port 17005 left by Apache Tomcat/6.0.20 after having to terminate it forcefully, since it has run away due to remote JDBC resource contention on another server. A normal Tomcat stop / shutdown proves... (2 Replies)
Discussion started by: gjackson123
2 Replies
9. Programming
Hello everybody,
Years ago i left in stand-by a project of mine where the main program was supposed to send thousands ARP frames over the socket as fast as it could; but because of a programming issue i couldn't continue it.
2 days ago I decided to solve that issue.
The thing is, when the... (4 Replies)
Discussion started by: Zykl0n-B
4 Replies
10. Programming
Hello friends! i am writing a code in which i take inputs (numbers) from user and count the total number of positive, negative and zeros entered. I need to clear my standard input buffer before scanf() command. My compiler is completely ignoring the fflush(stdin) command. its not even showing any... (1 Reply)
Discussion started by: Abhishek_kumar
1 Replies
MALLOC(3) BSD Library Functions Manual MALLOC(3)
NAME
malloc, calloc, realloc, free -- general purpose memory allocation functions
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <stdlib.h>
void *
malloc(size_t size);
void *
calloc(size_t number, size_t size);
void *
realloc(void *ptr, size_t size);
void
free(void *ptr);
DESCRIPTION
The malloc() function allocates size bytes of uninitialized memory. The allocated space is suitably aligned (after possible pointer coer-
cion) for storage of any type of object.
The calloc() function allocates space for number objects, each size bytes in length. The result is identical to calling malloc() with an
argument of ``number * size'', with the exception that the allocated memory is explicitly initialized to zero bytes.
The realloc() function changes the size of the previously allocated memory referenced by ptr to size bytes. The contents of the memory are
unchanged up to the lesser of the new and old sizes. If the new size is larger, the value of the newly allocated portion of the memory is
undefined. Upon success, the memory referenced by ptr is freed and a pointer to the newly allocated memory is returned. Note that realloc()
may move the memory allocation, resulting in a different return value than ptr. If ptr is NULL, the realloc() function behaves identically
to malloc() for the specified size.
The free() function causes the allocated memory referenced by ptr to be made available for future allocations. If ptr is NULL, no action
occurs.
RETURN VALUES
The malloc() and calloc() functions return a pointer to the allocated memory if successful; otherwise a NULL pointer is returned and errno is
set to ENOMEM.
The realloc() function returns a pointer, possibly identical to ptr, to the allocated memory if successful; otherwise a NULL pointer is
returned, and errno is set to ENOMEM if the error was the result of an allocation failure. The realloc() function always leaves the original
buffer intact when an error occurs.
The free() function returns no value.
EXAMPLES
When using malloc(), be careful to avoid the following idiom:
if ((p = malloc(number * size)) == NULL)
err(EXIT_FAILURE, "malloc");
The multiplication may lead to an integer overflow. To avoid this, calloc() is recommended.
If malloc() must be used, be sure to test for overflow:
if (size && number > SIZE_MAX / size) {
errno = EOVERFLOW;
err(EXIT_FAILURE, "allocation");
}
When using realloc(), one must be careful to avoid the following idiom:
nsize += 50;
if ((p = realloc(p, nsize)) == NULL)
return NULL;
Do not adjust the variable describing how much memory has been allocated until it is known that the allocation has been successful. This can
cause aberrant program behavior if the incorrect size value is used. In most cases, the above example will also leak memory. As stated ear-
lier, a return value of NULL indicates that the old object still remains allocated. Better code looks like this:
newsize = size + 50;
if ((p2 = realloc(p, newsize)) == NULL) {
if (p != NULL)
free(p);
p = NULL;
return NULL;
}
p = p2;
size = newsize;
SEE ALSO
madvise(2), mmap(2), sbrk(2), alloca(3), atexit(3), getpagesize(3), memory(3), posix_memalign(3)
For the implementation details, see jemalloc(3).
STANDARDS
The malloc(), calloc(), realloc() and free() functions conform to ISO/IEC 9899:1990 (``ISO C90'').
BSD
May 3, 2010 BSD