Date: Sun, 13 Apr 2003 23:43:09 -0400 From: Louis LeBlanc <leblanc+freebsd@keyslapper.org> To: FreeBSD Users <questions@FreeBSD.ORG> Subject: Re: SIGNAL 11 ==> core dump Message-ID: <20030414034308.GB51491@keyslapper.org> In-Reply-To: <001401c30204$8353d560$ca0110ac@vinyl.tkvbp.com> References: <3E99D109.760DBD0D@jaymax.com> <001401c30204$8353d560$ca0110ac@vinyl.tkvbp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/13/03 05:34 PM, Kliment Andreev sat at the `puter and typed: > > What is the best method for doing a 'core debug' with BSD. Which is > > SIGNAL 11, is it SIGSEGV? > > Signal 11 usually means that something is wrong with your hardware settings. > Check all IRQ conflicts. If there aren't any, probably something is wrong > with the memory. Uh, don't I wish. Any C or C++ program that tries to dereference a null pointer, overwrite the end of a buffer, or free memory that has already been freed can easily cause a signal 11. And they aren't always easy to track down either. But yeah. Hardware is usually the problem if you're talking about different processes going SEGV without any discernable pattern. Lou -- Louis LeBlanc leblanc@keyslapper.org Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ snappy repartee: What you'd say if you had another chance.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030414034308.GB51491>