This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
- From: "martin at minimum dot se" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 18 Sep 2014 14:56:29 +0000
- Subject: [Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
- Auto-submitted: auto-generated
- References: <bug-17384-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17384
--- Comment #17 from molsson <martin at minimum dot se> ---
The things that makes me believe that I do have symbols available is A) it says
"Yes" in the "Syms" column of the libblink_web.cr.so line in "info
sharedlibrary", also if I trace all executed commands during the build process
I can see that RenderFullscreen.cpp is built with "-g" parameter.
FWIW, the list of CFLAGS (I'm skipping a metric ton of -D and -I switches) is:
-fstack-protector --param=ssp-buffer-size=4 -Werror -fno-exceptions
-fno-strict-aliasing -Wall -Wno-unused-parameter
-Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC
-Wno-unused-local-typedefs -march=armv7-a -mtune=generic-armv7-a
-mfpu=vfpv3-d16 -mfloat-abi=softfp -mthumb -fno-tree-sra -fno-partial-inlining
-fno-early-inlining -fno-tree-copy-prop -fno-tree-loop-optimize
-fno-move-loop-invariants -fno-caller-saves -Wno-psabi -mthumb-interwork
-ffunction-sections -funwind-tables -g -fstack-protector -fno-short-enums
-finline-limit=64 -Wa,--noexecstack
--sysroot=..../third_party/android_tools/ndk/platforms/android-14/arch-arm
-isystem..../third_party/android_tools/ndk/sources/cxx-stl/stlport/stlport -O0
-g -funwind-tables -fdiagnostics-color=always -fno-rtti -fno-threadsafe-statics
-fvisibility-inlines-hidden -Wsign-compare -Wno-c++0x-compat -Wno-abi
-std=gnu++11 -Wno-narrowing -Wno-literal-suffix
Notably, I'm also not passing -fomit-frame-pointer for this file at least (if I
grep for "omit-frame-pointer" I see several hits in the chromium tree but I'm
not sure which platforms or files etc use it).
Also, I can put a breakpoint on certain other functions like for example
base::debug::TaskAnnotator::RunTask() and there I can use "next" without
problems so there seems to be something special with
blink::RenderFullScreen::createPlaceholder() or possibly with one of the
functions it calls. Maybe something with inlining, or maybe because it's
static, not sure.
I will try to put some breakpoints near the unwind selection tomorrow and get
back with more info on that.
--
You are receiving this mail because:
You are on the CC list for the bug.