From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31147 invoked by alias); 7 Sep 2012 13:26:29 -0000 Received: (qmail 31092 invoked by uid 22791); 7 Sep 2012 13:26:28 -0000 X-SWARE-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_XF X-Spam-Check-By: sourceware.org Received: from mail-ie0-f169.google.com (HELO mail-ie0-f169.google.com) (209.85.223.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 07 Sep 2012 13:26:15 +0000 Received: by iec9 with SMTP id 9so5733526iec.0 for ; Fri, 07 Sep 2012 06:26:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.193.202 with SMTP id hq10mr24035837igc.35.1347024374387; Fri, 07 Sep 2012 06:26:14 -0700 (PDT) Received: by 10.64.61.65 with HTTP; Fri, 7 Sep 2012 06:26:14 -0700 (PDT) Date: Fri, 07 Sep 2012 13:26:00 -0000 Message-ID: Subject: how to see DAR (data access register) on ppc using gdb 7.0.1 on Linux? From: Stefan Puiu To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00011.txt.bz2 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 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.