Project

General

Profile

Actions

Bug #358

closed

Native Debugging in Eclipse fails with ndk r8-crystax-1

Added by Timo Bußhaus over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Category:
build
Target version:
Start date:
05/28/2013
Due date:
% Done:

100%

Estimated time:
CPU Architecture:
armeabi
Host OS:
Windows
Toolchain:
gcc-4.6, gcc-4.7
Android version:
CrystaX Version:

Description

I switched the NDK from android-ndk-r7-crystax-5.beta3 to the new android-ndk-r8-crystax-1 and native debugging in Eclipse fails with the error message:

Failed to execute MI command:
-file-exec-and-symbols C:/Projekte/Android/CISdroid_unstable/CISdroid/obj/local/armeabi/app_process
Error message from debugger back end:
I'm sorry, Dave, I can't do that. Symbol format `elf32-littlearm' unknown.

Actions #1

Updated by Dmitry Moskalchuk about 7 years ago

  • Target version set to 10.0.0
Actions #2

Updated by Alexander Zhukov almost 7 years ago

  • Assignee set to Alexander Zhukov
Actions #3

Updated by Alexander Zhukov over 6 years ago

  • Status changed from Open to In Progress
Actions #4

Updated by Alexander Zhukov over 6 years ago

  • Target version deleted (10.0.0)
Actions #5

Updated by Dmitry Moskalchuk over 6 years ago

  • Priority changed from Normal to High
Actions #6

Updated by Alexander Zhukov over 6 years ago

  • Target version set to 10.2.0
Actions #7

Updated by Alexander Zhukov over 6 years ago

  • Status changed from In Progress to Done
  • % Done changed from 0 to 100

Debugging with ndk-gdb from a command line works now for all supported platforms, i.e linux, mac, windows.
Debugging with Eclipse does not work because of ADT plugin issues.
See this topic for example: https://code.google.com/p/android/issues/detail?id=57865

NB Debugging with Eclipse does not work for Google's NDK too as of r10d.

Actions #8

Updated by Alexander Zhukov over 6 years ago

  • Status changed from Done to Closed
Actions

Also available in: Atom PDF