public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: acahalan@cs.uml.edu (Albert D. Cahalan)
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: silly [< >] and other excess
Date: Sat, 25 Nov 2000 12:11:15 +0000 (GMT)	[thread overview]
Message-ID: <200011251211.eAPCBF019116@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200011251026.eAPAQKG210983@saturn.cs.uml.edu> from "Albert D. Cahalan" at Nov 25, 2000 05:26:20 AM

Albert D. Cahalan writes:
> Yes. Don't you look at the raw data anyway?

I look at the raw stack data from time to time, but mostly I want
the backtrace, PC and LR converted into something more meaningful,
and I don't want the extra clutter of that particular raw data.

> In theory yes, but in practice no. Your kernel isn't a significant
> portion of your address space, so the chance of random data being
> looked up successfully is very low. Maybe a 1% chance on 32-bit
> hardware, and far less on 64-bit hardware.

Not so.  This is my point; on the ARM, when you get stuff like stack
and registers dumped, a lot of the hex numbers can look very much like
addresses in kernel space; most of them are data object symbols and
the like.  There can be a lot of these, and suddenly you'd end up with
most of the System.map being output because something in the dump
somewhere looks like its a symbol.

> Somebody else posted a reasonable hack for the [<>] problem.
> His proposal involved letting multiple values share the same
> markers, something like this:

Yep, now that is one idea I like!
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         Russell King        rmk@arm.linux.org.uk      --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+                                                     --- -+-
  /   |               THE developer of ARM Linux              |+| /|\
 /  | | |                                                     ---  |
    +-+-+ -------------------------------------------------  /\\\  |
-
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/

  parent reply	other threads:[~2000-11-25 12:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 19:00 silly [< >] and other excess Andries.Brouwer
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                 ` Russell King [this message]
2000-11-27 22:02                   ` silly [< >] and other excess 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=200011251211.eAPCBF019116@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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