dump_syms and Android

2,149 views
Skip to first unread message

Mateusz Półrola

unread,
Sep 14, 2012, 6:27:15 AM9/14/12
to google-brea...@googlegroups.com
Hi how I can generate symbols file for Android library, because using dymp_syms gives me an error: file is neither a fat binary file nor a Mach-O object file.

Ted Mielczarek

unread,
Sep 14, 2012, 6:38:03 AM9/14/12
to google-brea...@googlegroups.com
Currently none of the dump_syms tools support cross-OS symbol dumping,
and it sounds like you're trying to dump symbols from an Android ELF
binary on OS X. You'll have to build Breakpad on Linux to get a Linux
dump_syms that will work on those ELF binaries.

This would not be an insurmountable problem to fix, but we'd probably
have to ship our own copies of system headers like elf.h.

-Ted

Mateusz Półrola

unread,
Sep 14, 2012, 7:19:50 AM9/14/12
to google-brea...@googlegroups.com, t...@mielczarek.org

Ok, thanks I will try this.

Daniel Ryan

unread,
Jul 7, 2013, 11:29:15 PM7/7/13
to google-brea...@googlegroups.com
Is this still the case? I'm guessing so if I'm getting the exact error. 
I'm building the NDK library on my Mac, so I had hope I could debug on my Mac. I don't have access to Linux; my work only uses Mac. 
Is there a solution one can do? Or a time frame for it to be fixed? 

Brian

unread,
Dec 11, 2013, 8:06:58 PM12/11/13
to google-brea...@googlegroups.com
Likewise.  Most of our Android app build servers are Macs, so we'd like to run a Mac version of dump_syms that would generate sym files as part of the build output.

If this cannot be provided in the source repository, what would we need to do to enable on our own branch?

Ted Mielczarek

unread,
Dec 11, 2013, 8:20:16 PM12/11/13
to google-brea...@googlegroups.com
On 12/11/2013 8:06 PM, Brian wrote:
> Likewise. Most of our Android app build servers are Macs, so we'd
> like to run a Mac version of dump_syms that would generate sym files
> as part of the build output.
>
> If this cannot be provided in the source repository, what would we
> need to do to enable on our own branch?
This isn't something anyone at Google or Mozilla is likely to fix, since
we don't have a need for it. It's probably not a really hard problem,
you may be able to coerce things to try to build by configuring with
--enable-tools on a Mac. Things are likely to blow up, but you only
really have to fix the compilation of dump_syms. I don't believe it does
anything too fancy, most of the DWARF-parsing code is built for Mac as well.

If you get it working we'd take a patch.

-Ted

Jay Soffian

unread,
Dec 18, 2014, 7:59:21 PM12/18/14
to google-brea...@googlegroups.com
On Wednesday, December 11, 2013 8:20:16 PM UTC-5, Ted Mielczarek wrote:
This isn't something anyone at Google or Mozilla is likely to fix, since
we don't have a need for it. It's probably not a really hard problem,
you may be able to coerce things to try to build by configuring with
--enable-tools on a Mac. Things are likely to blow up, but you only
really have to fix the compilation of dump_syms. I don't believe it does
anything too fancy, most of the DWARF-parsing code is built for Mac as well.

If you get it working we'd take a patch.

I realize this thread is over a year old, but I recently had the same need. Here's a first take at a patch - https://breakpad.appspot.com/8684002/

j. 
Reply all
Reply to author
Forward
0 new messages