From: michel.dagenais@polymtl.ca (Michel Dagenais)
Subject: [ltt-dev] Question about instruction pointer and address attributes
Date: Fri, 19 Nov 2010 16:42:53 -0500 (EST) [thread overview]
Message-ID: <1803619724.178551290202973690.JavaMail.root@srv12.zimbra.polymtl.ca> (raw)
In-Reply-To: <20101119144305.17237jyflt1dt2o8@www.usherbrooke.ca>
> 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
That makes sense, most system calls first go through libc.
> Another example, inside a TRAP, I got two addresses,
> ip=0xffffffff812c722b and address=0x7fa4fba2cbc0, those two addresses
> First, what is the difference between ip and address attribute? And
> wow does the ip can be converted back to the process address space?
The ip is probably in the kernel space. The address could be the data access address causing a trap.
next prev parent reply other threads:[~2010-11-19 21:42 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
2010-11-19 21:42 ` Michel Dagenais [this message]
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=1803619724.178551290202973690.JavaMail.root@srv12.zimbra.polymtl.ca \
--to=michel.dagenais@polymtl.ca \
/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