Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: "Turny Dávid" <Turny.David@stud.u-szeged.hu>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sourceware.org
Subject: Re: "cannot find bounds of current function"
Date: Tue, 17 Oct 2006 20:20:00 -0000	[thread overview]
Message-ID: <1161116425.14535.385.camel@localhost.localdomain> (raw)
In-Reply-To: <20061017205007.199nqbqk0so0o48w@www.stud.u-szeged.hu>

On Tue, 2006-10-17 at 20:50 +0200, Turny Dávid wrote:
> Hi,
> 
> Sorry, I see just now when I execute the continue or step or next  
> command then the openOCD deamon write an error message:
> 
> error: arm7_9_common.c:1771 arm7_9_read_memory():memory read caused data abort
> 
> What is this? :) I dont understand. 

Personally,  I'm not familiar with openOCD.

One thing you might do at this point would be, before you 
tell gdb to "continue", tell it "set debug remote 1".  This
will turn on "remote protocol debugging", so gdb will echo
all traffic between the debugger and the target to the console.

You can then see exactly what was the last thing that happened
before you got the above error.

You should consult the gdb doc to understand the remote protocol, 
but here's a quick hint: messages that begin with "M" are memory
writes, and messages that begin with "m" are memory reads.  You
are looking for a memory read (apparently).  The hexadecimal address
of the memory access will be the first number following the "M" or 
"m".



  reply	other threads:[~2006-10-17 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 18:50 Turny Dávid
2006-10-17 20:20 ` Michael Snyder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17 18:23 Turny Dávid
2006-10-16  1:05 Turny Dávid
2006-10-16  9:16 ` Daniel Jacobowitz
2006-10-17  2:37 ` Michael Snyder

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=1161116425.14535.385.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=Turny.David@stud.u-szeged.hu \
    --cc=drow@false.org \
    --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