Hi,
I was also facing "03:48 E/ddm-Addr2Line: Error while trying to start
arm-eabi-addr2line process for library /system/lib/libssl.so" error.
Then I provided "out\target\product\surf\symbols\system\lib" in DDMS-
>file>preference->device->default images save dir.

But I couldn’t see any file or method name populating. Please let me
know if I am missed anything.

And I believe by using native heap tab information I can able to get
memory leak information about my native shared object. Please comment
on it.

Thank you,
Raghu



On Aug 18, 8:49 pm, clikx <click...@gmail.com> wrote:
> Hi Fadden.
>
> I am using own tree.
>
> I am still facing the problem of the columns not populating.
> I am using the standalone ddms (and adb).
>
> I am getting the following error for all the libraries.
> 03:48 E/ddm-Addr2Line: Error while trying to start arm-eabi-addr2line
> process for library /system/lib/libssl.so
>
> I am not able to find; which file, the path preferences of "/<path>/
> arm-eabi-addr2line" and "/out/target/product/<prod>/symbols/system/
> lib/" are to be updated.
>
> Regards
> Clikx
>
> On Aug 7, 10:20 pm, fadden <fad...@android.com> wrote:> On Aug 6, 9:13 pm, 
> clikx <click...@gmail.com> wrote:
>
> > > Required some more information i.e
> > > The coloumns 'File' and 'Line' (only) are not populated. What needs to
> > > be enabled to get data in 'File' and 'Line' coloumns.
>
> > DDMS needs the "symbols" directory under "out" in a build tree.  The
> > stand-alone DDMS is set up so that, if you run it out of the same
> > source tree that was used to build the code on the device, it will
> > automatically find the copies of the shared libraries that have
> > symbols in them.  (And it automatically uses the symbols from
> > libc_debug.so rather than libc.so.)  The shared objects on the device
> > have had their symbols stripped.
>
> > Are you building your own tree or using the SDK?
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to