02-11-2002
I am sorry, I fogot to mention that this is Tru64 UNIX 40f.
We had to change the shm-max parameter based on
Oracle's recommendation to 2139095040 (2GB-8MB).
But this was almost > a year ago and this is the first time.... we have seen any such message in the syslog.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a doubt with an error message, and i want to be sure if this is a normal situation or not.
Situation: I was formating and installing a SCSI 36Gb HD with UNIX SCO 5.05, the problem happens when is making the division and filesystem on disk 1, and the message error is "Exit value 139... (1 Reply)
Discussion started by: jav_v
1 Replies
2. Programming
dear all ,
iam trying to compile a progam using gcc compiler on a sun 280 R machine running solaris 9 .
iam getting an error in the last step when the compiler tries to link the objects , although the compiler executes some applicarions that contains no objects smoothly,
the error that... (1 Reply)
Discussion started by: ppass
1 Replies
3. Programming
Hi,
I just pulled out my code from source control, then I compiled, the compilation is successful at that time.
Then I modified one of the source file, Then I compiled, I got the following error
ld: fatal: Symbol referencing errors. No output written to ../../CM/bin/cato
Before... (1 Reply)
Discussion started by: sarwan
1 Replies
4. Programming
i am trying to compile my program using a makefile and i keep getting this message:
Undefined first referenced
symbol in file
main
/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.3/crt1.o
ld: fatal: Symbol referencing errors. No output written to prog5
collect2: ld returned 1 exit status
***... (2 Replies)
Discussion started by: betterdayz
2 Replies
5. UNIX for Advanced & Expert Users
while running a script to process a file , it ended in termination . I able to find from the logs that it ended due to the error : fatal: record too large 20480 . Then I tried lots to fix the issue and left in vain . Can any one help me in finding reason for it ? . If you provide me a solution , I... (1 Reply)
Discussion started by: sakthifire
1 Replies
6. Web Development
Any clues on how to get rid of this PHP error?
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /website/www/includes/functions_manpages.php on line 58
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71... (4 Replies)
Discussion started by: Neo
4 Replies
7. Shell Programming and Scripting
While running script I am getting an error like
Few lines in data are not being processed.
After googling it I came to know that adding such line would give some memory to it
ini_set("memory_limit","64M");
my input file size is 1 GB.
Is that memory limit is based on RAM we have on... (1 Reply)
Discussion started by: elamurugu
1 Replies
8. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
9. UNIX for Beginners Questions & Answers
Hello. I'm writing an awk script that looks at a .csv file and calculates the weighted grade based on the scores and categories in the file. I keep getting a fatal division by zero attempted error and I know what it means but I've been looking over the code for awhile and am not sure what is... (4 Replies)
Discussion started by: Eric7giants
4 Replies
LEARN ABOUT OPENSOLARIS
xfree
XMALLOC(3pub) C Programmer's Manual XMALLOC(3pub)
NAME
xmalloc, xrealloc, xfree, xstrdup, xmemdup, memdup - memory allocation functions for Publib
SYNOPSIS
#include <publib.h>
void *xmalloc(size_t bytes);
void *xrealloc(void *ptr, size_t bytes);
void xfree(void *ptr);
char *xstrdup(const char *string);
void *memdup(const void *mem, size_t bytes);
void *xmemdup(const void *mem, size_t bytes);
DESCRIPTION
These functions are utility functions for memory allocation from the publib library. xmalloc, xrealloc, and xfree are error checking ver-
sions of the standard library routines malloc, realloc, and free, respectively. They are guaranteed to never return unless there was no
problem: if, for example, xmalloc is unable to allocate the requested amount of memory, it prints an error message and terminates the pro-
gram. Hence, the caller does not need to check for a NULL return value, and the code that calls these functions is simpler due to the lack
of error checks.
Similarly, xstrdup is an error checking version of the common (though not standard) strdup routine, which creates a duplicate of a string
by allocating memory for the copy with malloc. (For systems that lack strdup, publib provides one in its portability module; it is always
declared in <publib.h>.)
memdup is similar to strdup, it creates a copy of an arbitrary memory area (the arguments are a pointer to the beginning of the area, and
its size) by allocating memory for the copy with malloc. xmemdup is its error checking version.
NOTE
xmalloc and xrealloc treat a request to allocate a block of 0 bytes as an error. xrealloc will allow its first argument to be NULL.
SEE ALSO
publib(3), malloc(3), strdup(3)
AUTHOR
Lars Wirzenius (lars.wirzenius@helsinki.fi)
Publib C Programmer's Manual XMALLOC(3pub)