Right now, profile-symbolicate.py requires a local build. It would be good to have the ability to pull the .so files off of the device, then a local build wouldn't be required. Apparently, there is a way to add some symbolic information to the .so files which isn't as big as full debug information (based on IRC conversation with BenWa on Dev 7 around 11:11) So we also need to compare the output using the 2 methods.
Yes, when stripped we can chose to strip the debug information but leave the symbols intact. That means that the binary we'll ship will have symbol describing the address range but wont be usable in GDB like custom build. The symbol table doesn't get mapped to memory so it wont put any memory pressure either. See https://bugzilla.mozilla.org/show_bug.cgi?id=719536#c6 for my analysis. It likely is very similar for b2g. It's worth having regular release with symbols that can be used for profiling without requiring a custom build. In desktop all nightly build get symbols but we strip them in aurora/release.
Is this still desired?
I think so. It would be useful when you don't have a build tree.
(In reply to Dave Hylands [:dhylands] from comment #3) > I think so. It would be useful when you don't have a build tree. Do you think you could drive it, or do you know of someone who could?
(In reply to John Ford [:jhford] -- please use 'needinfo?' instead of a CC from comment #4) > (In reply to Dave Hylands [:dhylands] from comment #3) > > I think so. It would be useful when you don't have a build tree. > > Do you think you could drive it, or do you know of someone who could? This particular bug isn't blocking anything, so it's lower priority than the blocking bugs. It's been quite a while since I haven't had any blocking bugs to work on...