Closed GoogleCodeExporter closed 9 years ago
we usually simply run
./a.out 2>&1 | asan_symbolize.py| c++filt
Isn't that enough?
The new symbolizer is coming, so asan_symbolize.py will eventually get
deprecated.
https://code.google.com/p/address-sanitizer/wiki/CallStack
Original comment by konstant...@gmail.com
on 25 Jan 2013 at 2:04
People often don't know that they should run it like that and I got this
question more than once already. I think in most, if not all cases, there is no
benefit in showing the mangled trace, because it is at most useful for
debugging problems in the symbolizer, but not for reading the actual trace. If
that is the case, then the symbolizer should demangle on its own by default.
But if the new symbolizer is coming soon anyway, then I hope it'll be able to
do this and we don't need to change the python script right now :)
Original comment by decoder...@googlemail.com
on 25 Jan 2013 at 2:06
Note filtering the whole ASan logs through c++filt sometimes produces silly
results. We must demangle only function names with c++filt in asan_symbolize.py
or llvm-symbolizer.
Original comment by gli...@chromium.org
on 25 Jan 2013 at 2:23
FTR: Using a pipe for c++filt is unnecessary on Linux - you can additionally
pass "-C" to addr2line process or "--demangle" to llvm-symbolizer.
Original comment by samso...@google.com
on 25 Jan 2013 at 3:28
http://llvm.org/viewvc/llvm-project?rev=175429&view=rev adds flag -d to do what
samsonov@ suggested in comment #4
This does not seem applicable to atos on MacOS
Original comment by konstant...@gmail.com
on 18 Feb 2013 at 8:04
Adding Project:AddressSanitizer as part of GitHub migration.
Original comment by ramosian.glider@gmail.com
on 30 Jul 2015 at 9:13
Original issue reported on code.google.com by
decoder...@googlemail.com
on 25 Jan 2013 at 2:01