Compiling in Debugging Flags

[Chris Maness]

Chris Maness wrote:
> Bill Moran wrote:
>> In response to Chris Maness <chris at chrismaness.com>:
>>
>>  
>>>> Then, ensure the sysctls in the kernel are all frobbed to allow 
>>>> coredumps.
>>>> Specifically:
>>>> kern.coredump: 1
>>>> kern.sugid_coredump: 1
>>>>       
>>> What is frobbed?
>>>     
>>
>> http://en.wikipedia.org/wiki/Frob
>>
>> You need to learn important things like this if you're going to get
>> anywhere in this business ...
>>
>>   
> sysctl -a | grep core
> kern.corefile: %N.core
> kern.nodump_coredump: 0
> kern.coredump: 1
> kern.sugid_coredump: 0
> <6>pid 36665 (conftest), uid 0: exited on signal 11 (core dumped)
> <6>pid 97013 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 48143 (conftest), uid 0: exited on signal 12 (core dumped)
> <6>pid 69261 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 30477 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 17468 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 72511 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 88618 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 91921 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 48962 (httpd), uid 0: exited on signal 11 (core dumped)
> <6>pid 96510 (httpd), uid 0: exited on signal 11 (core dumped)
> debug.elf32_legacy_coredump: 0
>
> How do I change the the values?  Also, where do the files go by default?
>
Never mind, I figured it out.  Stay tuned, and I'll have some output.

Chris