It would be less painful primarily because my codebase already has
cross-compilation for compiler-rt set up, and cross-compiling llvm is a
whole new can of worms. But I'll take a look at the buildbots and see what
I can get working. Just wanted to make sure I wasn't missing something
simple in terms of an in-process symbolizer.

On Thu, Aug 24, 2017, 2:42 PM 'Evgenii Stepanov' via address-sanitizer <
[email protected]> wrote:

> Building internal symbolizer would not be any less painful than the
> external one. It's the same code built with the same toolchain, and
> then some more on top.
>
> This bot does it on every build:
> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-android/
> but since it builds several targets in parallel, it's hard to extract
> cmake arguments from the output. Look in the zorg repo, it is quite
> simple.
>
> I don't remember what the issues with internal symbolizer on Android
> are. It might even work out of the box.
>
> On Thu, Aug 24, 2017 at 11:13 AM, Francis Ricci <[email protected]>
> wrote:
> > I'm not getting symbolicated backtraces on android, and the android
> > developer docs suggest building and installing a cross-compiled
> > llvm-symbolizer
> > (https://source.android.com/devices/tech/debug/asan#symbolization). I
> can do
> > that, but I expect it will be a pain.
> >
> > It looks like there was some discussion a couple years ago about porting
> the
> > in-process symbolizer to android
> > (https://groups.google.com/forum/#!topic/llvm-dev/qivubL_sEGw), is that
> > something that has been finished? If so, do I need to do anything
> special to
> > use it (I'm using ASAN_OPTIONS=symbolize=1, but that's it currently). I'm
> > only running on fairly powerful devices, so I'm not too worried about the
> > performance cost of in-process symbolication.
> >
> > Francis
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "address-sanitizer" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "address-sanitizer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to