Friends I am Trying this code to call main Recursively But It is showing segmentation errot
#include<stdio.h>
int main()
{
int i;
for(i=0;i<10;i++)
{
if(i==5)
{
exit(0);
}
else
{
main();
}
}
} (7 Replies)
hello everyone..
am having problem with my so-called main makefile
all my files are in the same folder, i was planning to make a single makefile that would make two executable but I got some errors so I separated them and used
now i was wondering if I could create a single makefile... (6 Replies)
We compile the sendmail.cf file using main.mc. I have managed to place all of our configuration options in main.mc without a problem, with the exception of one.
I want to have the HelpFile commented out by default in sendmail.cf. How can I instruct main.mc to place an entry for HelpFile in... (1 Reply)
Lately there have been a lot of one-liners posted in "ruby" on the apparent assumption that mainstream unix or Linux come with "ruby. They don't.
What is "ruby"?
What platforms and Operating System versions are supported?
The syntax for "ruby" seems remarkably obscure compared with say "awk"... (13 Replies)
It seems $? can only contain one byte. see below:
int main()
{
return 0x12345678;
}
After I run the code and check the $? value it output 120, obviously it is the decimal of the last byte of 0x12345678. And if I return a value less than 255, the $? value seems right.
Why? and... (3 Replies)
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Hi All,
Could you please suggest books for learning ruby and python language ?
Thanks,
Pravin (1 Reply)
Discussion started by: pravin27
1 Replies
LEARN ABOUT CENTOS
object::deadly::_unsafe
Object::Deadly::_unsafe(3) User Contributed Perl Documentation Object::Deadly::_unsafe(3)NAME
Object::Deadly::_unsafe - Implementation for the deadly object
METHODS
"$obj->DESTROY"
The DESTROY method doesn't die. This is defined so it won't be AUTOLOADed or fetched from UNIVERSAL.
"$obj->isa"
"$obj->can"
"$obj->version"
"$obj->DOES"
"$obj->import"
"$obj->require"
"$obj->use"
"$obj->blessed"
"$obj->dump"
"$obj->peek"
"$obj->refaddr"
"$obj->exports"
"$obj->moniker"
"$obj->plural_moniker"
"$obj->which"
"$obj->AUTOLOAD"
Each of AUTOLOAD, a named list of known UNIVERSAL functions and then a query for everything currently known are all implemented with
"Object::Deadly->get_death" to prevent anything from sneaking through to a successful call against something in UNIVERSAL.
That list of functions are what core perl uses plus a bunch from CPAN modules including UNIVERSAL, UNIVERSAL::require, UNIVERSAL::dump,
UNIVERSAL::exports, UNIVERSAL::moniker, UNIVERSAL::which. That's just the list as it exists today. If someone else creates a new one
and you load it, be sure to do it *prior* to loading this module so I can have at least a chance at noticing anything it's loaded.
SEE ALSO
Object::Deadly, Object::Deadly::_safe
perl v5.16.3 2006-09-25 Object::Deadly::_unsafe(3)