We recently had a few requests to ship symbols with our prebuilt Android builds, like:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt...
...see build artifacts:
target/product/pandaboard/system.tar.bz2 target/product/pandaboard/boot.tar.bz2 target/product/pandaboard/userdata.tar.bz2
We could simply tar up the out/ directory of the build and post that as well, but I thought we may want to do something a little different. Since the intended target is to allow DS-5 to resolve symbols on prebuilt Android builds is there a better way to post this so that things "just work."
Morning,
On Thu, 2012-06-07 at 19:42 +0100, Zach Pfeffer wrote:
We recently had a few requests to ship symbols with our prebuilt Android builds, like:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt...
...see build artifacts:
target/product/pandaboard/system.tar.bz2 target/product/pandaboard/boot.tar.bz2 target/product/pandaboard/userdata.tar.bz2
We could simply tar up the out/ directory of the build and post that as well, but I thought we may want to do something a little different. Since the intended target is to allow DS-5 to resolve symbols on prebuilt Android builds is there a better way to post this so that things "just work."
Let me involve two more people to the discussion - Bernie and Scott. Both are vitally interested in the subject :-)
Cheers!
Paweł
On Fri, 2012-06-08 at 10:27 +0100, Pawel Moll wrote:
Morning,
On Thu, 2012-06-07 at 19:42 +0100, Zach Pfeffer wrote:
We recently had a few requests to ship symbols with our prebuilt Android builds, like:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt...
...see build artifacts:
target/product/pandaboard/system.tar.bz2 target/product/pandaboard/boot.tar.bz2 target/product/pandaboard/userdata.tar.bz2
We could simply tar up the out/ directory of the build and post that as well, but I thought we may want to do something a little different. Since the intended target is to allow DS-5 to resolve symbols on prebuilt Android builds is there a better way to post this so that things "just work."
Let me involve two more people to the discussion - Bernie and Scott. Both are vitally interested in the subject :-)
... and Lukas as well.
Paweł
+Robert Kaye who had actually asked for the debug symbols .
I don't think we need the debug symbols. Loading the libraries from the system tar ball was sufficient for me to profile using ds-5 .Alternately if we build a "userdebug" buildtype image instead of "eng" we need not load the libraries also for profiling using DS-5 .The functions are resolved by DS-5 from the debug build.
On 8 June 2012 15:12, Pawel Moll pawel.moll@arm.com wrote:
On Fri, 2012-06-08 at 10:27 +0100, Pawel Moll wrote:
Morning,
On Thu, 2012-06-07 at 19:42 +0100, Zach Pfeffer wrote:
We recently had a few requests to ship symbols with our prebuilt Android builds, like:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt...
...see build artifacts:
target/product/pandaboard/system.tar.bz2 target/product/pandaboard/boot.tar.bz2 target/product/pandaboard/userdata.tar.bz2
We could simply tar up the out/ directory of the build and post that as well, but I thought we may want to do something a little different. Since the intended target is to allow DS-5 to resolve symbols on prebuilt Android builds is there a better way to post this so that things "just work."
Let me involve two more people to the discussion - Bernie and Scott. Both are vitally interested in the subject :-)
... and Lukas as well.
Paweł
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
The debug symbols (kernel and user space) would be handy as it would allow us to dig down into the source code views, and additionally we could then also use the DS-5 debugger to debug.
It will be good to have the kernel headers so that we could rebuild the gator driver. (handy as DS-5 and Linaro releases are not guaranteed to be in sync)
Best regards, Lukas
From: Vishal Bhoj [mailto:vishal.bhoj@linaro.org] Sent: 08 June 2012 11:01 To: Pawel Moll Cc: Zach Pfeffer; linaro-android; Bernard Ogden; Scott Douglass; Lukas Snetler; Robert Kaye Subject: Re: Android Symbols and DS-5
+Robert Kaye who had actually asked for the debug symbols .
I don't think we need the debug symbols. Loading the libraries from the system tar ball was sufficient for me to profile using ds-5 .Alternately if we build a "userdebug" buildtype image instead of "eng" we need not load the libraries also for profiling using DS-5 .The functions are resolved by DS-5 from the debug build.
On 8 June 2012 15:12, Pawel Moll <pawel.moll@arm.commailto:pawel.moll@arm.com> wrote: On Fri, 2012-06-08 at 10:27 +0100, Pawel Moll wrote:
Morning,
On Thu, 2012-06-07 at 19:42 +0100, Zach Pfeffer wrote:
We recently had a few requests to ship symbols with our prebuilt Android builds, like:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt...https://android-build.linaro.org/builds/%7Elinaro-android/panda-ics-gcc47-tilt-tracking-blob/
...see build artifacts:
target/product/pandaboard/system.tar.bz2 target/product/pandaboard/boot.tar.bz2 target/product/pandaboard/userdata.tar.bz2
We could simply tar up the out/ directory of the build and post that as well, but I thought we may want to do something a little different. Since the intended target is to allow DS-5 to resolve symbols on prebuilt Android builds is there a better way to post this so that things "just work."
Let me involve two more people to the discussion - Bernie and Scott. Both are vitally interested in the subject :-)
... and Lukas as well.
Paweł
_______________________________________________ linaro-android mailing list linaro-android@lists.linaro.orgmailto:linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On Fri, Jun 8, 2012 at 12:01 PM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
+Robert Kaye who had actually asked for the debug symbols .
I don't think we need the debug symbols. Loading the libraries from the system tar ball was sufficient for me to profile using ds-5 .Alternately if we build a "userdebug" buildtype image instead of "eng" we need not load the libraries also for profiling using DS-5 .The functions are resolved by DS-5 from the debug build.
aren't the symbols nicely sorted into their own "directory" so we could tar them into a separate system-dbg.tar.bz2 ?
I kind of feel reluctant to create an additional build for this. I want dbgsym for exactly the builds we output/release...
On 8 June 2012 06:21, Alexander Sack asac@linaro.org wrote:
On Fri, Jun 8, 2012 at 12:01 PM, Vishal Bhoj vishal.bhoj@linaro.org wrote:
+Robert Kaye who had actually asked for the debug symbols .
I don't think we need the debug symbols. Loading the libraries from the system tar ball was sufficient for me to profile using ds-5 .Alternately if we build a "userdebug" buildtype image instead of "eng" we need not load the libraries also for profiling using DS-5 .The functions are resolved by DS-5 from the debug build.
aren't the symbols nicely sorted into their own "directory" so we could tar them into a separate system-dbg.tar.bz2 ?
I kind of feel reluctant to create an additional build for this. I want dbgsym for exactly the builds we output/release...
Yeah, me to. I think if we just tar up the kernel headers and various directories in out/ then it'll all work.
We'll get something kicked off to make this a reality.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
linaro-android@lists.linaro.org
-
Alexander Sack -
Lukas Snetler -
Pawel Moll -
Vishal Bhoj -
Zach Pfeffer