From owner-freebsd-arch@FreeBSD.ORG  Sat Feb  9 10:46:02 2013
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 22232933;
 Sat,  9 Feb 2013 10:46:02 +0000 (UTC)
 (envelope-from utisoft@gmail.com)
Received: from mail-ie0-x22a.google.com (ie-in-x022a.1e100.net
 [IPv6:2607:f8b0:4001:c03::22a])
 by mx1.freebsd.org (Postfix) with ESMTP id E19F42AC;
 Sat,  9 Feb 2013 10:46:01 +0000 (UTC)
Received: by mail-ie0-f170.google.com with SMTP id c11so6085565ieb.15
 for <multiple recipients>; Sat, 09 Feb 2013 02:46:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=fJYDIzuDhWt7MVuZMkxJWgey77+gkZjVLGtfMCW6RrA=;
 b=nXmVyOMKIBphD30wYHkson6S/Iz2ocP/4E23T+UVtB1XDKuZDELiRMvCzGpEAVVtoZ
 9OCRCELGIIvBXc55DTXWz1WaZOxyMuk0BpthoasMfLkVZ3dot4jGSetomMgYYvmd9f82
 CSGVH5jKqXaNNLBRHNFunQd8eEEazCi7YdHICkjZvZ9MB02eP8OxEsMCglcQO2bJwHIm
 yaT3lLN1x7TTrdSO5kCa2VHM5oxmB2CveVfd7aqcH6hWqYQsBujSNY4EncaoFpkPqbIE
 NHFAojoMgSqYzRFeiGMLifu4RH6GcQCidXMpxpR5KVsbfc1G5hS3Fq8mv0lyi2w8r/pL
 ko2Q==
MIME-Version: 1.0
X-Received: by 10.50.197.170 with SMTP id iv10mr4295325igc.62.1360406761620;
 Sat, 09 Feb 2013 02:46:01 -0800 (PST)
Received: by 10.64.16.73 with HTTP; Sat, 9 Feb 2013 02:46:01 -0800 (PST)
Received: by 10.64.16.73 with HTTP; Sat, 9 Feb 2013 02:46:01 -0800 (PST)
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>
Date: Sat, 9 Feb 2013 10:46:01 +0000
Message-ID: <CADLo83_HfA4FGR0xNzHpPNPGee3QHG3PB8ZQVXGci=TvOB6kZQ@mail.gmail.com>
Subject: Re: Proposal: Unify printing the function name in panic messages()
From: Chris Rees <utisoft@gmail.com>
To: Andriy Gapon <avg@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: Kirk McKusick <mckusick@mckusick.com>,
 Christoph Mallon <christoph.mallon@gmx.de>, freebsd-arch@freebsd.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 10:46:02 -0000

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