Consultor Eletrônico

Status: Unverified

GOAL:

Why is Progress not generating a core file on Solaris?

GOAL:

How to enable a core file on Solaris?

GOAL:

How to get a core dump on Solaris?

GOAL:

If a core file is always created when a process is killed, what could prevent a core from being created on Solaris?

FACT(s) (Environment):

Sun Solaris SPARC

FIX:

On Solaris a core file is created each time a process is killed. One can manually create a core file by simply performing a kill -8 against the process PID. In addition to a core file, Progress will always try to create a protrace (protrace.PID) file as well. Both files are created in the same directory and time stamps should be consistent between the two.

Progress will always give notification when a core file is created. Warning error 439 will appear in the client and/or server log file.

** Save file named core for analysis by Progress Software Corporation. (439)

So then if a core file is always created when a process is killed, what could prevent a core from being created on Solaris?

Sun prevents setuid executables from generating core files when they are run by a user other than the superuser. This can be seen by doing the following:

1. Run _progres (owned by root, with 4775 permissions + setuid enabled) as a user other than root.
2. Terminate the process via kill ?8.
3. You will find no core created.

However if you, log in and run the _progress as root and then kill the process, a core file will be generated.

You can workaround this issue by doing the following

1. Turn off the setuid bit on the executable that you are running, i.e., _progress, _proapsv etc?, however this is not recommended.

2. Or use the coreadm utility (a Sun tool) to enable setuid programs to produce core files. This can be done by reviewing the documentation of sun found at;

How to use the coreadm utility (http://docs.sun.com/app/docs/doc/805-7229/6j6q8svhr?a=view).