perform stack overflow Post: 302570837

6 More Discussions You Might Find Interesting

1. BSD

stack overflow in function psync_status Abort (core dumped)

I am running Open BSD 3.8 (3.5 upgrade) on a Pent Pro. 200, 64 Megs Ram, Nvedia Vanta TNT 16 Megs, Realtech 8139 Nic. When running ifconfig -a I get this error back. I've run searches on google no deal. I can get Stack overflow or psync, but not both. So I would really like to know how to fix it. ...

2. HP-UX

Problem with stack overflow

Hi, I get a problem with stack overflow on HP-UX, when running a C program. Pid 28737 received a SIGSEGV for stack growth failure. Possible causes: insufficient memory or swap space, or stack size exceeded maxssiz. The possible cause i found, was that the definition of a structure had...

3. AIX

IBM xlf "parser stack overflow" error

Hello, Does anybody know how to increase IBM xlf parser stack to get rid of the "parser stack overflow" error? Thanks Ping

4. Ubuntu

Stack overflow i guess while insmod

I have built kernel 2.6.35 on my Ubuntu system with some specific requirement. I also built some app defined module with the same kernel. I booted up the built version and I find it did not work properly as there is some gui and other modules missing problem. But the system booted up and I did...

5. AIX

perform stack overflowed

Help! I have an AIX system that has a power outage. When I logged in as root and got the system up and running it all looked ok. But.....when a user tries to log in they receive the error: The perform stack has overflowed OP=2117 PC=2124 E=46 in emmcshflif icrun is finished How can I fix...

6. Hardware

Stack Overflow Questions Tags Users Badges Unanswered Ask Question Ask for the explanation of types

I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks! RAM on disk drive controllers 1 firmware 2 speed matching buffer 3 prefetching buffer 4 cache

LEARN ABOUT OSX

halt

REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME

     halt, reboot -- stopping and restarting the system

SYNOPSIS

     halt [-lnqu]
     reboot [-lnq]

DESCRIPTION

     The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
     respectively, halt or restart the system.	The action is logged, including entering a shutdown record into the wtmp(5) file.

     When the system is halted with the halt command, the system is powered off.

     The options are as follows:

     -l      The halt or reboot is not recorded in the system log.  This option is intended for applications such as shutdown(8), that call reboot
	     or halt and log this themselves.

     -n      The file system cache is not flushed.  This option should probably not be used.

     -q      The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
	     option is not specified).	This option should probably not be used.

     -u      The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
	     UPS (uninterruptible power supply) can forcibly remove power.  This simulates a dirty shutdown to permit a later automatic power on.
	     OS X uses this mode automatically with supported UPSs in emergency shutdowns.

     Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
     doom and cleanly terminating specific programs.

SIGTERM TO SIGKILL INTERVAL

     The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time.  Programs are expected to take only enough time to
     flush all dirty data and exit.  Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this func-
     tionality.

SEE ALSO

     wtmp(5), shutdown(8), sync(8)

HISTORY

     A reboot utility appeared in Version 6 AT&T UNIX.

BSD
								   June 9, 1993 							       BSD