Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] Question about instruction pointer and address	attributes
Date: Fri, 19 Nov 2010 16:40:25 -0500	[thread overview]
Message-ID: <20101119214025.GA31212@Krystal> (raw)
In-Reply-To: <20101119144305.17237jyflt1dt2o8@www.usherbrooke.ca>

* Francis Giraldeau (Francis.Giraldeau at USherbrooke.ca) wrote:
> Hi,
>
> I want to relate trace events to source code. For testing, I did a small 
> C program that does a file access. In the event kernel.syscall_entry 
> sys_access, I got the instruction pointer ip=0x7fa4fba26ee7. I dumped the 
> process memory map from /proc/$PID/maps, and this address doesn't fit in 
> the process memory space. It's somewhat close to libc addresses, that are 
> in the range of 0x7f6471f56000-0x7f64724fc000.
>
> Another example, inside a TRAP, I got two addresses,  
> ip=0xffffffff812c722b

This looks like the vDSO.

 and address=0x7fa4fba2cbc0, those two addresses  
> doesn't map in the process space.
>
> First, what is the difference between ip and address attribute? And wow 
> does the ip can be converted back to the process address space?

Make sure you cat the /proc/$PID/maps from the exact same process you
gather the trace from, because the addresses at which the libraries are
loaded and the stack is located are randomised between executions.

Cheers,

Mathieu

>
> Cheer,
>
> Francis
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




  reply	other threads:[~2010-11-19 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 19:43 Francis Giraldeau
2010-11-19 21:40 ` Mathieu Desnoyers [this message]
2010-11-19 21:42 ` Michel Dagenais
2010-12-01  2:17 Francis Giraldeau

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=20101119214025.GA31212@Krystal \
    --to=compudj@krystal.dyndns.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