There are many possible reasons, I will try to list them all, but I could easily have forgotten some: The core would have been larger than the current limit. Verify if there is a limit and try to disable it. In bash, sh and similar shells type ulimit -a to see the current limits and type ulimit -S -c unlimited to disable the limit, finally verify that it has been disabled. In tcsh, csh and similar shells use limit and limit coredumpsize unlimited.

Sounds like something on your system is misconfigured. Everytime I've had reports like this (works as root, not as user), it's turned out to be /tmp was unwriteable or something equally improbable. The easiest way to find out is to use the debugger and tell me where Expect is dumping core. (If you don't understand this statement, ask a local C or C++ programmer.) an aside, you should be using the most recent version of Expect (currently 5.22.1). But I don't know of any problems in 5. See similar questions...

In Apache version 1.2, the error log message about dumped core includes the directory where the dump file should be located. However, many Unixes do not allow a process that has called setuid() to dump core for security reasons; the typical Apache setup has the server started as root to bind to port 80, after which it changes UIDs to a non-privileged user to serve requests. Dealing with this is extremely operating system-specific, and may require rebuilding your system kernel. See similar questions...

If you just want a program to terminate now and dump core, you can use the SIGABRT signal. This signal can be send from another process using kill. Or it can be send by the process itself using, kill, raise, or abort. If you want a core dump without killing the process, things start getting more tricky. You can create a child process by using the fork system call, and let the child dump core. The init program actually does this in its signal handlers. See similar questions...

In Linux 1.3.57 and later, the format of /proc/meminfo was changed in a way that the implementation of free doesn't understand. See similar questions...

Core dumps can occur for a variety of reasons. However - a number of people have reported core dumps occuring in the gatherer before any objects are fetched. This is most often caused by the site having a malformed robots.txt file. If you're attempting to fetch a page http://www.blob.org/blobby/blah.html then Harvest will first check the robots.txt file at http://www.blob.org/robots.txt The correct format of this file is documented at http://info.webcrawler.com/mak/projects/robots/norobots-rfc. See similar questions...

In general no, at least not unless you provide more details about the code location where Apache dumped core. What is usually always required in order to help you is a backtrace (see next question). Without this information it is mostly impossible to find the problem and help you in fixing it. See similar questions...

STM requires that the Motif and X Windows libraries be present on the system. If they are not, error messages similar to the following are displayed: If you see a message like this (the particular version of the library, which is ".4" in this case, may vary), load the Motif libraries from the HP-UX OS media. See similar questions...

If you have the source you can easily add a statement early in main to enable the dumpable flag. #include <sys/prctl.h> ... /* The last three arguments are just padding, because the * system call requires five arguments. */ prctl(PR_SET_DUMPABLE,1,42,42,42); If anybody know a clean and secure way to get core dumps from suid executables without a recompile please tell me about it. See similar questions...

There can be a lot of reasons why a core dump can occur, of course. Ranging from buggy third-party modules, over buggy vendor libraries up to a buggy mod_ssl version. But the above situation is often caused by old or broken vendor DBM libraries. To solve it either build mod_ssl with the built-in SDBM library (specify --enable-rule=SSL_SDBM at the APACI command line) or switch from SSLSessionCache dbm: to the newer SSLSessionCache shm:'' variant (after you have rebuilt Apache with MM, of course). See similar questions...

Make sure you have debugging symbols available in at least Apache. On platforms where you use GCC/GDB you have to build Apache+mod_ssl with ''OPTIM="-g -ggdb3"'' to achieve this. On other platforms at least ''OPTIM="-g"'' is needed. Startup the server and try to produce the core-dump. For this you perhaps want to use a directive like ''CoreDumpDirectory /tmp'' to make sure that the core-dump file can be written. You then should get a /tmp/core or /tmp/httpd.core file. See similar questions...

Not necessarily. If you have GNU sed 3.0 you should downgrade it to 2.05. From the 'README' at prep.ai.mit.edu: sed 3.0 has been withdrawn from distribution. It has major revisions, which mostly seem to be improvements; but it turns out to have bugs too which cause trouble in some common cases. Tom Lord won't be able to work fixing the bugs until May. So in the mean time, we've decided to withdraw sed 3.0 from distribution and make version 2.05 once again the recommended version. See similar questions...

The problem could be a number of things. Try testing your user-defined function in a stand alone test program first. See similar questions...

This is a Version 6.0 compiler problem. Users of the Version 6.0 compiler can encounter a GEM ASSERTION on code containing the expression b ? true : false. S: Upgrade to the latest version. If the problem persists, please report it to customer support. Be prepared to supply a preprocessed file along with the compiler flags that you are using. See similar questions...

If your model has integer/binary/semi-cont/SOS variables then version 5 can solve your problem. In version 4, the implemented branch-and-bound algorithm puts its branches on the stack and that can result in a stack overflow when it is a tough model. Version 5 doesn't put the branches on the stack anymore and because of that, this error is solved. See similar questions...

In LITE mode, Memory Advisor performs memory filling to help you detect errors. When you allocate new memory, Memory Advisor fills that memory with a nonzero pattern (0xFE by default). If your program relies on that value being zero, and that value is a very large number, your program may dump core. By using a debugger on your program or core file, you can determine why your program dumped core and correct an otherwise undetected bug. See similar questions...

Just because your code runs on UNIX does not mean that it will run unmodified on Windows. In our experience, your code may really have a latent bug (or non-portable code) which simply does not manifest on UNIX. To debug such situations: Set the "stop always" state for the Access Violation exception in the Debug/Exceptions menu. On a segmentation violation, a pop-up dialog box will let you launch the debugger at the location of the fault. See similar questions...

I'll just quote the ePSXe FAQ... "To dump a PlayStation BIOS, you need a GameShark or Action replay and a PC comms link. To start, you need either a real Caetla module or go ... search [the Internet] for "Caetla" (it's a BIOS replacement for your module, so properly read the included documentation before installing it!!). See similar questions...

There are no RV dump stations in the South Platte District campgrounds. The nearest dump stations are Fairplay Texaco, Fairplay, CO 719/836-2021; Lake George Cabins & RV Park, 8966 County Road 90, Lake George Colorado 80827; phone & fax 719/748-3822. Follow this link for more listings http://www.coloradodirectory.com/. See similar questions...