On 11/27/13 00:36, Jakub Jelinek wrote:
Use libbacktrace for libsanitizer's symbolization (will need tweaking,
depending on next libsanitizer merge, whether the corresponding
sanitizer_common changes are upstreamed or not, and perhaps to compile
libbacktrace sources again with renamed function names and other tweaks
- different allocator, only subset of files, etc.; but, there is a P1
bug for this anyway):
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02055.html
Isn't libsanitizer maintained outside GCC? In which case making
significant changes of this nature ought to be avoided.
While I see the benefit in what you're doing, I question if we want to
go down this road.
Or is it the case that the build stuff in libsanitizer is ours and the
only shared bits you'r hacking up are sanitizer_symbolizer_posix_libcdep.cc?
jeff
