Date: Mon, 11 Feb 2013 13:20:00 -0800 From: Adrian Chadd <adrian@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: Kirk McKusick <mckusick@mckusick.com>, Christoph Mallon <christoph.mallon@gmx.de>, Andriy Gapon <avg@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Proposal: Unify printing the function name in panic messages() Message-ID: <CAJ-Vmokt%2Byq7WMpW0S5Kzy7y1EFGU6g6pHt=QuoZ-zs%2BG-U0BQ@mail.gmail.com> In-Reply-To: <201302111203.19422.jhb@freebsd.org> References: <51141E33.4080103@gmx.de> <201302111105.58186.jhb@freebsd.org> <51191EC1.9000303@gmx.de> <201302111203.19422.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Whoa, whoa. Are you seriously trying to argue that having a consistent file:line isn't a really helpful addition to panic messages? Yes, you can get it via the crash IP and use of binutils on the kernel image. But with modules? You have to fire up kgdb, and that requires a dump _and_ a kgdb that matches the kernel image in question. Even if you don't add it to the panic message, having that information passed into panic() so it can print out a file:line would be great. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmokt%2Byq7WMpW0S5Kzy7y1EFGU6g6pHt=QuoZ-zs%2BG-U0BQ>