Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion dump_syms and Android

Received: by 10.205.139.2 with SMTP id iu2mr340825bkc.7.1347619086164;
        Fri, 14 Sep 2012 03:38:06 -0700 (PDT)
X-BeenThere: google-breakpad-discuss@googlegroups.com
Received: by 10.204.13.17 with SMTP id z17ls4101353bkz.5.gmail; Fri, 14 Sep
 2012 03:38:05 -0700 (PDT)
Received: by 10.204.129.81 with SMTP id n17mr342927bks.3.1347619085446;
        Fri, 14 Sep 2012 03:38:05 -0700 (PDT)
Received: by 10.204.129.81 with SMTP id n17mr342926bks.3.1347619085430;
        Fri, 14 Sep 2012 03:38:05 -0700 (PDT)
Return-Path: <ted.mielcza...@gmail.com>
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181])
        by gmr-mx.google.com with ESMTPS id e23si93763bks.0.2012.09.14.03.38.04
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 14 Sep 2012 03:38:04 -0700 (PDT)
Received-SPF: pass (google.com: domain of ted.mielcza...@gmail.com designates 209.85.217.181 as permitted sender) client-ip=209.85.217.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ted.mielcza...@gmail.com designates 209.85.217.181 as permitted sender) smtp.mail=ted.mielcza...@gmail.com; dkim=pass header...@gmail.com
Received: by lbbgk1 with SMTP id gk1so2796860lbb.26
        for <google-breakpad-discuss@googlegroups.com>; Fri, 14 Sep 2012 03:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=g73hU0cGdOaxAxB26pGdy4x1Po7E0vp1SR0slnO5wsk=;
        b=iFFMFJ4IPrnsAxwLU1kaXSUWC6al2R/zQritKxEcHMGgNWFn2XwfHWff9lpH1CnkZB
         Ue+okRIh80zFhArdtHzBlpK7klvXg2scFUJW1W9nkJwDzCZEWrqDmB5OPETNmoy05vON
         qte/pvmPAiWoveMRP1Zh1rlTXSHfzBit5tEVNKVs4cOlLzpmX61MqaxQz/0y7KMfn5jA
         AnfTeHQkygD92J3tn4pbF6EBJ5ZurZozM47+mIEOdDuidewm+hLywMUYXvxHpYEJirZv
         zbhWxQrD4vGQPLkYU9MkhGza8Qe2rIDq1TKvTLNKoA7lXzQb+bjq2Kl01cFbOWyOUECJ
         SQPQ==
MIME-Version: 1.0
Received: by 10.112.86.232 with SMTP id s8mr923688lbz.117.1347619084085; Fri,
 14 Sep 2012 03:38:04 -0700 (PDT)
Sender: ted.mielcza...@gmail.com
Received: by 10.112.64.164 with HTTP; Fri, 14 Sep 2012 03:38:03 -0700 (PDT)
In-Reply-To: <e1574007-850b-4fe4-84c8-1ca0182d057e@googlegroups.com>
References: <e1574007-850b-4fe4-84c8-1ca0182d057e@googlegroups.com>
Date: Fri, 14 Sep 2012 06:38:03 -0400
Message-ID: <CAKkNbbZE3e_d1-TUZk_mYDEQoLeoC+R4kPcxF9fXrfZDz5a...@mail.gmail.com>
Subject: Re: dump_syms and Android
From: Ted Mielczarek <t...@mielczarek.org>
To: google-breakpad-discuss@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 14, 2012 at 6:27 AM, Mateusz P=C3=B3=C5=82rola <mateo343@gmail.=
com> wrote:
> 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.

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