From: Andrew Morton <andrewm@uow.edu.au>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Keith Owens <kaos@ocs.com.au>, Hugh Dickins <hugh@veritas.com>,
Paul Gortmaker <p_gortmaker@yahoo.com>,
linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] a more efficient BUG() macro
Date: Sun, 18 Feb 2001 12:50:21 +1100 [thread overview]
Message-ID: <3A8F2A5D.D272DA8@uow.edu.au> (raw)
In-Reply-To: <20010218013353.A1331@werewolf.able.es> <19480.982457293@ocs3.ocs-net> <3A8F266F.AFA01552@uow.edu.au>, <3A8F266F.AFA01552@uow.edu.au>; from andrewm@uow.edu.au on Sun, Feb 18, 2001 at 02:33:35 +0100 <20010218023714.C951@werewolf.able.es>
"J . A . Magallon" wrote:
>
> On 02.18 Andrew Morton wrote:
> >
> > __BASE_FILE__ does this. It expands to the thing which you
> > typed on the `gcc' command line.
> >
> ..
> > 3 at a.c
> > 3 at a.c
>
> I also thought that, but look at the line numbers...wrong and repeated.
Sure. There's no __BASE_LINE__.
I don't think providing file-n-line in BUG() provides much utility. Just
remove it. Replace it with "please feed the following into ksymoops".
next prev parent reply other threads:[~2001-02-18 1:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 8:51 [PATCH] a more efficient BUG() macro Paul Gortmaker
2001-02-17 12:26 ` Manfred Spraul
2001-02-17 12:57 ` Pauline Middelink
2001-02-17 13:15 ` Hugh Dickins
2001-02-17 14:22 ` J . A . Magallon
2001-02-17 15:14 ` J . A . Magallon
2001-02-17 17:04 ` [PATCH] conditionalize __io_virt_debug Jeff Garzik
2001-02-18 0:01 ` [PATCH] a more efficient BUG() macro Keith Owens
2001-02-18 0:33 ` J . A . Magallon
2001-02-18 0:48 ` Keith Owens
2001-02-18 1:33 ` Andrew Morton
2001-02-18 1:37 ` J . A . Magallon
2001-02-18 1:50 ` Andrew Morton [this message]
2001-02-18 1:47 ` Keith Owens
2001-02-18 14:27 ` Andi Kleen
2001-02-17 16:37 ` J . A . Magallon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A8F2A5D.D272DA8@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=hugh@veritas.com \
--cc=jamagallon@able.es \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox