mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org, akpm@linux-foundation.org
Subject: [patch 0/2]  Improve the markup_oops.pl script
Date: Tue, 13 Jan 2009 15:01:03 +0000	[thread overview]
Message-ID: <20090113150103.085c6eb6@infradead.org> (raw)

Hi,

the following 2 patches enhance the markup_oops.pl script in two ways
Patch 1: Add support for putting register values in the asm dump
Patch 2: Add support for 64 bit X86

The output (on a 32 bit OS with a "make me oops" example module) looks like
the pasted dump; for the instruction where the oops happened, as well as
a few instructions before that where the dumper can determine the register value.
the value is appended on said line.


 	if (bar-1) { 
 f8436012:	8b 45 fc             	mov    -0x4(%ebp),%eax 
 f8436015:	48                   	dec    %eax 
 f8436016:	74 09                	je     f8436021 <foo_bar+0x21> 
 		bar = bar * 5; 
 f8436018:	8b 45 fc             	mov    -0x4(%ebp),%eax 
 f843601b:	8d 04 80             	lea    (%eax,%eax,4),%eax  |  %eax => 0 
 f843601e:	89 45 fc             	mov    %eax,-0x4(%ebp)     |  %eax = 0 
 	} 
 	*foo = 1; 
*f8436021:	c6 02 01             	movb   $0x1,(%edx)         |  %edx = 0 <--- faulting instruction
 	return bar; 
 f8436024:	8b 45 fc             	mov    -0x4(%ebp),%eax 
 } 
 f8436027:	c9                   	leave   
 f8436028:	c3                   	ret     
  
--
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

             reply	other threads:[~2009-01-13 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 15:01 Arjan van de Ven [this message]
2009-01-13 15:01 ` [PATCH 1/2] scripts: add x86 register parser to markup_oops.pl Arjan van de Ven
2009-02-15 10:31   ` Sam Ravnborg
2009-01-13 15:02 ` [PATCH 2/2] scripts: add x86 64 bit support to the markup_oops.pl script Arjan van de Ven
2009-02-15 10:31   ` Sam Ravnborg

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=20090113150103.085c6eb6@infradead.org \
    --to=arjan@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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

Powered by JetHome