public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Puiu <stefan.puiu@gmail.com>
To: gdb@sourceware.org
Subject: how to see DAR (data access register) on ppc using gdb 7.0.1 on Linux?
Date: Fri, 07 Sep 2012 13:26:00 -0000	[thread overview]
Message-ID: <CACKs7VAAXQC-Ln7yRBb3GobNBruCHD7Td=qVs9aVkoEVs_v0Pw@mail.gmail.com> (raw)

Hi,

I'm trying to debug a crash on our embedded Linux platform using:

# gdb --version

warning: Can not parse XML syscalls information; XML support was
disabled at compile time.
GNU gdb (GDB) 7.0.1
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-750-linux-gnu".

I was trying to see the PPC registers after a crash:

    (gdb) info registers
     r0             0x1034875e       271877982
     r1             0x7fffed30       2147478832
     r2             0xfd7f7a0        265811872
     [...]
     pc             0xf18d718        0xf18d718
     msr            0xd032   53298
     cr             0x80000848       2147485768
     lr             0xf18d6f8        0xf18d6f8
     ctr            0xf235d90        253975952
     xer            0x20000000       536870912
     orig_r3        0x26     38
     trap           0x300    768

I noticed that the DAR (data access register) is not present here -
I'm trying to see the memory address whose access caused the crash. I
only see the trap register, which confirms that there was an invalid
memory access, but that's it as far as I can tell.

I know the contents of the DAR are printed in case of kernel crashes
(in oops dumps), is there a way to view the register from gdb? 'info
register dar' doesn't work...

Thanks in advance,
Stefan.

             reply	other threads:[~2012-09-07 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 13:26 Stefan Puiu [this message]
2012-09-07 13:44 ` Luis Gustavo
2012-09-07 17:12 ` Pedro Alves

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='CACKs7VAAXQC-Ln7yRBb3GobNBruCHD7Td=qVs9aVkoEVs_v0Pw@mail.gmail.com' \
    --to=stefan.puiu@gmail.com \
    --cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).