All of lore.kernel.org
 help / color / mirror / Atom feed
From: getarunks@gmail.com (Arun Sudhilal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to get object virtual address from a kernel core dump
Date: Tue, 22 Mar 2016 17:09:08 +0530	[thread overview]
Message-ID: <CABOM9ZrcecujZBfyLXSK8SXPFmkZGWRNH6Y-ZnuxQEZJVHJ15Q@mail.gmail.com> (raw)
In-Reply-To: <CA+9drc69Rwbyi31ixFdmTqGu9yptpPS3qvD7BnDaKHNK8W11vA@mail.gmail.com>

Hello Zach,

On Fri, Mar 18, 2016 at 3:28 PM, Mohammad Y. Zachariah <eng.myz@gmail.com>
wrote:

> Hello everyone,
>
> I'm taking the way of analysing kernel core dumps as a learning approach
> using 'crash tool'. One of the interesting crash commands is 'struct' which
> can print kernel struct definition and/or the actual contents of the
> structure.
>
> According to struct help page, I need the virtual address of the struct in
> order to view/print its contents, for example:
>
>     crash> mm_struct.pgd ffff810022e7d080 -px
>       pgd_t *pgd = 0xffff81000e3ac000
>       -> {
>            pgd = 0x2c0a6067
>          }
>
> My question is how to find the mm_struct address "ffff810022e7d080" in the
> above example in the first place??
>

crash tool has a 'ps'  command, which outputs all the task and their task
struct address.

Thanks,
Arun

>
> Thank you for your help in advance.
> Zach
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160322/676f2c2d/attachment.html 

  reply	other threads:[~2016-03-22 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  9:58 How to get object virtual address from a kernel core dump Mohammad Y. Zachariah
2016-03-22 11:39 ` Arun Sudhilal [this message]
2016-03-23  3:41 ` Buland Kumar Singh
2016-03-22 11:03 Manoj Nayak

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=CABOM9ZrcecujZBfyLXSK8SXPFmkZGWRNH6Y-ZnuxQEZJVHJ15Q@mail.gmail.com \
    --to=getarunks@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.