Date: Fri, 12 Sep 2008 13:23:32 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= <patfbsd@davenulle.org> To: "Riaan Kruger" <riaank@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Driver debugging help Message-ID: <20080912132332.4f9e9056@baby-jane-lamaiziere-net.local> In-Reply-To: <85c4b1850809110259w56f3439cua37359b3dc39f909@mail.gmail.com> References: <85c4b1850809110259w56f3439cua37359b3dc39f909@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le Thu, 11 Sep 2008 11:59:05 +0200, "Riaan Kruger" <riaank@gmail.com> a écrit : > I am looking for hints to debug a driver I am working on. I get a > page fault when running the driver intensively. The stack trace from > the kernel dump only goes up to a free command which I suspect is > being called from my driver. No matter what I do I cannot get a more > "complete" stack trace. kgdb says something about the stack being > corrupt when I do a backtrace/stack trace. > > Is there anything else I could use to help me pinpoint where I am > going wrong? > > I have tried memguard but it has given me no information. Maybe I am > using it incorrectly. Did you try redzone(9)? If the stack is corrupted it could be a buffer overflow. You can ask on freebsd-hackers or freebsd-drivers mailing lists. And may be show us the code? Regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080912132332.4f9e9056>