Date: Sat, 9 Feb 2013 10:46:01 +0000 From: Chris Rees <utisoft@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: Kirk McKusick <mckusick@mckusick.com>, Christoph Mallon <christoph.mallon@gmx.de>, freebsd-arch@freebsd.org Subject: Re: Proposal: Unify printing the function name in panic messages() Message-ID: <CADLo83_HfA4FGR0xNzHpPNPGee3QHG3PB8ZQVXGci=TvOB6kZQ@mail.gmail.com> In-Reply-To: <511622A2.2090601@FreeBSD.org> References: <51141E33.4080103@gmx.de> <511426B8.2070800@FreeBSD.org> <51160E06.1070404@gmx.de> <5116121E.1010601@FreeBSD.org> <511616AC.8080306@gmx.de> <511622A2.2090601@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 Feb 2013 10:19, "Andriy Gapon" <avg@freebsd.org> wrote: > > on 09/02/2013 11:28 Christoph Mallon said the following: > > On 09.02.2013 10:08, Andriy Gapon wrote: > >> In any case, you just search the code for the message and that's it. > > > > Often the messages contains parameters (%d, %s, ...) or are split into multiple lines to appease the ancient 80 columns god. > > These make it harder to grep. > > Having the /right/ name makes it easier to get to the right place. > > Having right tools for the search does that too. > And doesn't require any code churn. OK, which tool can one find a panic message split across lines in source code? I would find this very useful. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_HfA4FGR0xNzHpPNPGee3QHG3PB8ZQVXGci=TvOB6kZQ>