From: Steven Hanley <sjh@svana.org>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: addresses in xmon trace output?
Date: Thu, 28 Jun 2001 13:10:43 +1000 [thread overview]
Message-ID: <20010628131043.A913@wibble.net> (raw)
In-Reply-To: <20010627191103.A27680@nevyn.them.org>; from dmj+@andrew.cmu.edu on Wed, Jun 27, 2001 at 07:11:03PM -0700
On Wed, Jun 27, 2001 at 07:11:03PM -0700, Daniel Jacobowitz wrote:
> They're addresses all right. System.map lists the beginning of each
> function; those addresses will be somewhere in the middle. It's
> sorted; find the closest match before each.
okay, that was easy, although the first address doesnt seem to be in the map
anywhere, maybe I copied it down wrong I suppose.
[13:04:08] 30 shiva sjh ~>./findinsmap.pl /boot/System.map-2.4.6-pre3
c67b2098 c00e1bd8 c00e1080 c011f9df c00de590 c00de7ec c003b6a4 c0003b3c
Addr: c00e1bd8 A: c00e1aa8 B: c00e1cb0 Function: c00e1aa8 T alloc_skb
Addr: c00e1080 A: c00e1004 B: c00e1170 Function: c00e1004 T sock_alloc_send_skb
Addr: c011f9df A: c011f8b4 B: c011fc74 Function: c011f8b4 t unix_stream_sendmsg
Addr: c00de590 A: c00de4f4 B: c00de5c0 Function: c00de4f4 T sock_sendmsg
Addr: c00de7ec A: c00de758 B: c00de7fc Function: c00de758 t sock_write
Addr: c003b6a4 A: c003b5dc B: c003b6f0 Function: c003b5dc T sys_write
Addr: c0003b3c A: c0003b3c B: c0003bf0 Function: c0003b3c T ret_from_syscall_1
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-06-28 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 2:03 addresses in xmon trace output? Steven Hanley
2001-06-28 2:11 ` Daniel Jacobowitz
2001-06-28 3:10 ` Steven Hanley [this message]
2001-06-28 9:38 ` Benjamin Herrenschmidt
2001-06-28 12:45 ` Steven Hanley
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=20010628131043.A913@wibble.net \
--to=sjh@svana.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.net \
/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).