This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"


https://sourceware.org/bugzilla/show_bug.cgi?id=17384

--- Comment #24 from molsson <martin at minimum dot se> ---
At first I had this error printed saying "Cannot access memory at address 0x1"
but Ulrich Weigand's fix makes sure that this error is no longer printed. AFAIK
that fix did so by suppressing the printout and I don't know if gdb is meant to
attempt reading at 0x1 or not (sounds unlikely?) so I guess this attempted read
is a side affect of incorrect assumptions about the prologue it is trying to
analyze?

The main remaining bug for me is, as you say, that when I try to move through
this function using "next" commands, gdb gets stuck in a mode where it just
prints "Cannot find bounds of current function" without moving forward:

Breakpoint 1, blink::RenderFullScreen::createPlaceholder (this=0x7f038100,
style=..., frameRect=...) at
../../third_party/WebKit/Source/core/rendering/RenderFullScreen.cpp:188
188        if (style->width().isAuto())
(gdb) n
0x7a6f4ac0 in ?? () from
/media/ssd/src/opera/opera/chromium/src/out_generic_armv7/Debug/lib/libblink_web.cr.so
(gdb) n
Cannot find bounds of current function
(gdb) n
Cannot find bounds of current function
(gdb)

Also when I'm in this mode the "bt" looks like this:

(gdb) bt
#0  0x7a6f4ac0 in ?? () from
/media/ssd/src/opera/opera/chromium/src/out_generic_armv7/Debug/lib/libblink_web.cr.so
#1  0x7f038100 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]