dirkx 99/12/03 02:37:34
Modified: . debugging.html
Log:
Added setuid() / coreadm trick
Revision Changes Path
1.8 +19 -0 apache-devsite/debugging.html
Index: debugging.html
===================================================================
RCS file: /x3/home/cvs/apache-devsite/debugging.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- debugging.html 1998/10/09 23:09:17 1.7
+++ debugging.html 1999/12/03 10:37:32 1.8
@@ -23,6 +23,7 @@
<LI><A HREF="#truss">Using '<CODE>truss/trace/strace</CODE>' to
trace system calls and signals</A>
<LI><A HREF="#gcore">Getting the server to dump core</A>
+<LI><A HREF="#sol27">Solaris 2.7 and coredumps</A>
<LI><A HREF="#tcpdump">Getting and analyzing a TCP packet trace</A>
</OL>
@@ -275,7 +276,25 @@
and then look at the backtrace as discussed above for <a href="#gdb">gdb</a>.
<P>
+<H3><A NAME="sol27">Solaris 2.7 and coredumps</A></H3>
+On Solaris 2.7 use <b><code>coreadm</core></b> to make <code>setuid()</code>
+processes actually dump core. By default an setuid() process does not
+dump core.
+<br>
+Jens-Uwe Mager wrote:
+<blockquote>
+<i>For example I am using:<i/><p>
+<pre>
+ # coreadm
+ global core file pattern: /var/core/core.%f.%p.u%u
+ init core file pattern: core
+ global core dumps: enabled
+ per-process core dumps: enabled
+ global setid core dumps: enabled
+ per-process setid core dumps: enabled
+ global core dump logging: disabled
+</pre><blockquote>
<HR>
<H3><A NAME="tcpdump">Getting and analyzing a TCP packet trace</A></H3>
