This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: back into the thread....
- From: Sterling Augustine <saugustine at google dot com>
- To: Mark Manning <mark4th at gmail dot com>, gdb at sourceware dot org
- Date: Tue, 12 Nov 2013 15:10:04 -0800
- Subject: Re: back into the thread....
- Authentication-results: sourceware.org; auth=none
- References: <CAPGNrUX7TA-4eCrrP=sD9G6oNe5Kw=eWPm_jm-D7=9ZTz-v6BA at mail dot gmail dot com> <CAEG7qUx69s2cdp4XY3cGtAakDQAoSrGnbhgvvLxUzZG+rJKC_g at mail dot gmail dot com> <CAEG7qUyR8OZ=XGy0WwK=1UW46afS=e-67Hs=P3XToxKA1Q9+Pw at mail dot gmail dot com> <CAPGNrUX+pYbf5V7_p50uRy_3vL33ZYYJUCxwbzaFtw0sMc6nEA at mail dot gmail dot com> <CAPGNrUXsgV1=fZV1bpSMU33RZ-M7rdngSujZ22xwGOzTRdbkVA at mail dot gmail dot com> <CAPGNrUUYWR7AOcFwTSxdEZa47E8iUJyfhzhWs+6jSc2+f4xqrg at mail dot gmail dot 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.