Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sterling Augustine <saugustine@google.com>
To: Mark Manning <mark4th@gmail.com>, gdb@sourceware.org
Subject: Re: back into the thread....
Date: Tue, 12 Nov 2013 23:10:00 -0000	[thread overview]
Message-ID: <CAEG7qUwnjUVJ0sSMn3SaiojkuxTFfZVE7UaCc45OMiip=38exg@mail.gmail.com> (raw)
In-Reply-To: <CAPGNrUUYWR7AOcFwTSxdEZa47E8iUJyfhzhWs+6jSc2+f4xqrg@mail.gmail.com>

On Tue, Nov 12, 2013 at 3:04 PM, Mark Manning <mark4th@gmail.com> wrote:
> Built your example code, single stepped opcodes and executed the call
> to the poked in function.  the instant you execute the BL opcode into
> this function you get "Cannot access memory at address 0"

Please stop trimming the gdb list.

Does it run successfully without gdb at all? If it doesn't, then the
problem is somewhere in the system you are using.

If it does, then there is a bug in gdb here. File a bug either on
sourceware.org or with whomever supports your installation. As this is
likely very platform specific, you are likely to get better help from
your own support group.

Not much more we can do.


  parent reply	other threads:[~2013-11-12 23:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 22:09 Mark Manning
2013-11-12 22:42 ` Sterling Augustine
2013-11-12 22:47   ` Sterling Augustine
2013-11-12 22:59     ` Mark Manning
2013-11-12 23:00       ` Mark Manning
     [not found]         ` <CAPGNrUUYWR7AOcFwTSxdEZa47E8iUJyfhzhWs+6jSc2+f4xqrg@mail.gmail.com>
2013-11-12 23:10           ` Sterling Augustine [this message]
2013-11-12 23:09     ` Mark Manning
2013-11-13  6:48     ` Phi Debian
2013-11-13 12:29       ` Mark Manning
2013-11-13 12:54         ` Phi Debian
2013-11-13 12:59           ` Mark Manning
2013-11-14 17:19             ` Arnab Bhaduri
2013-11-12 22:55   ` Mark Manning
2013-11-13 10:34     ` 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='CAEG7qUwnjUVJ0sSMn3SaiojkuxTFfZVE7UaCc45OMiip=38exg@mail.gmail.com' \
    --to=saugustine@google.com \
    --cc=gdb@sourceware.org \
    --cc=mark4th@gmail.com \
    /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