mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: silly [< >] and other excess
Date: Wed, 22 Nov 2000 20:00:49 +0100 (MET)	[thread overview]
Message-ID: <UTC200011221900.UAA141657.aeb@aak.cwi.nl> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

    From rmk@flint.arm.linux.org.uk Wed Nov 22 19:20:52 2000

    > Andries.Brouwer@cwi.nl a écrit :
    > >  I also left something else
    > > that always annoyed me: valuable screen space (on a 24x80 vt)
    > > is lost by these silly [< >] around addresses in an Oops.
    > > They provide no information at all, but on the other hand
    > > cause loss of information because these lines no longer
    > > fit in 80 columns causing line wrap and the loss of the
    > > top of the Oops.]

    They provide no information to the human reader, but they tell klogd
    (and other tools) that the enclosed value is a kernel address that
    should be looked up in the System.map file and decoded into name +
    offset.

Of course. But since there is no information in [< >]
(their presence is syntactically determined, not semantically)
the tools you mention can be trivially patched to work without
this [< >] kludge. On the other hand, when the system panics
often klogd and similar nice programs do not run at all, and
hence are unable to do any good. All information available
is the information on the screen, and it is really a pity
to lose EIP and get a few parentheses instead.

Andries

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-22 19:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 19:00 Andries.Brouwer [this message]
2000-11-22 23:16 ` Russell King
2000-11-22 23:54   ` Albert D. Cahalan
2000-11-23  0:10     ` Russell King
2000-11-23  2:54       ` Albert D. Cahalan
2000-11-23  3:03         ` Keith Owens
2000-11-23 12:39           ` Albert D. Cahalan
2000-11-23 12:46             ` Alan Cox
2000-11-23 19:46             ` Russell King
2000-11-23  7:53         ` Russell King
2000-11-25  4:33           ` Albert D. Cahalan
2000-11-25  9:17             ` Russell King
2000-11-25 10:26               ` Albert D. Cahalan
2000-11-25 11:07                 ` Keith Owens
2000-11-25 12:18                   ` Albert D. Cahalan
2000-11-25 18:20                   ` silly [< >] Guest section DW
2000-11-24  8:09                     ` Pavel Machek
2000-11-25 12:11                 ` silly [< >] and other excess Russell King
2000-11-27 22:02                   ` Peter Samuelson
2000-11-27 22:35                     ` Keith Owens
2000-11-27 23:01                       ` bread in fat_access failed Nerijus Baliunas
2000-11-27 23:11                         ` Nerijus Baliunas
2000-11-28  9:16                       ` silly [< >] and other excess Christian Gennerat
2000-11-23  0:26     ` Russell King
2000-11-23  3:11       ` Ragnar Hojland Espinosa
2000-11-23  7:55         ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2000-11-23  2:24 Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16   ` Tuomas Heino
2000-11-23  0:38 Andries.Brouwer
2000-11-23  0:51 ` Alan Cox
2000-11-22 13:20 [PATCH] isofs/inode.c Andries.Brouwer
2000-11-22 13:42 ` silly [< >] and other excess Christian Gennerat
2000-11-22 16:00   ` Russell King
2000-11-22 22:22   ` Keith Owens
2000-11-22 23:32     ` Albert D. Cahalan

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=UTC200011221900.UAA141657.aeb@aak.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®