From: Christian Gennerat <christian.gennerat@vz.cit.alcatel.fr>
To: Andries.Brouwer@cwi.nl,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: silly [< >] and other excess
Date: Wed, 22 Nov 2000 14:42:05 +0100 [thread overview]
Message-ID: <3A1BCD2C.8F489FB3@vz.cit.alcatel.fr> (raw)
In-Reply-To: <UTC200011221320.OAA140634.aeb@aak.cwi.nl>
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.]
>
What a good idea!
Moreover, there is another problem in Oops:
the dumped stack is limited to 3 or 4 lines to prevent loss of information
but the call trace is unlimited and can loose all information,
and sometimes is printing forever!
--- arch/i386/kernel/traps.c.orig Mon Oct 2 20:57:01 2000
+++ arch/i386/kernel/traps.c Sun Nov 5 14:33:52 2000
@@ -142,11 +142,12 @@
* out the call path that was taken.
*/
if (((addr >= (unsigned long) &_stext) &&
+ (i<32) &&
(addr <= (unsigned long) &_etext)) ||
((addr >= module_start) && (addr <= module_end))) {
if (i && ((i % 8) == 0))
printk("\n ");
- printk("[<%08lx>] ", addr);
+ printk("%08lx ", addr);
i++;
}
}
And do not scroll the screen after the last printed line!
--- kernel/panic.c.orig Tue Jun 20 23:32:27 2000
+++ kernel/panic.c Sun Nov 5 07:53:04 2000
@@ -56,7 +56,7 @@
va_end(args);
printk(KERN_EMERG "Kernel panic: %s\n",buf);
if (in_interrupt())
- printk(KERN_EMERG "In interrupt handler - not syncing\n");
+ printk(KERN_EMERG "In interrupt handler - not syncing");
else if (!current->pid)
printk(KERN_EMERG "In idle task - not syncing\n");
else
-
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/
next prev parent reply other threads:[~2000-11-22 14:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 13:20 [PATCH] isofs/inode.c Andries.Brouwer
2000-11-22 13:42 ` Christian Gennerat [this message]
2000-11-22 16:00 ` silly [< >] and other excess Russell King
2000-11-22 22:22 ` Keith Owens
2000-11-22 23:32 ` Albert D. Cahalan
2000-11-22 19:00 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 12:11 ` Russell King
2000-11-27 22:02 ` Peter Samuelson
2000-11-27 22:35 ` Keith Owens
2000-11-28 9:16 ` Christian Gennerat
2000-11-23 0:26 ` Russell King
2000-11-23 3:11 ` Ragnar Hojland Espinosa
2000-11-23 7:55 ` Russell King
2000-11-23 0:38 Andries.Brouwer
2000-11-23 0:51 ` Alan Cox
2000-11-23 2:24 Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16 ` Tuomas Heino
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=3A1BCD2C.8F489FB3@vz.cit.alcatel.fr \
--to=christian.gennerat@vz.cit.alcatel.fr \
--cc=Andries.Brouwer@cwi.nl \
--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;
as well as URLs for NNTP newsgroup(s).