search

gopalshankar / address-sanitizer

Automatically exported from code.google.com/p/address-sanitizer
0 stars 0 forks source link

llvm-symbolizer should "Just Work" #134

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
(see also https://codereview.chromium.org/11348066/)
The users expect ASan to print understandable error logs without any additional 
env or output filtering.
Can we hardcode the compiler path somewhere so that ASan looks it up for 
llvm-symbolizer if the path hasn't been supplied via env?

Original issue reported on code.google.com by ramosian.glider@gmail.com on 11 Dec 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
>> Can we hardcode the compiler path
Instead, we should defeat the symbolizer to make it in-process.

Original comment by konstant...@gmail.com on 11 Dec 2012 at 2:55

GoogleCodeExporter commented 9 years ago 
Please remind me, have we considered putting the symbolizer into a .so?

Original comment by ramosian.glider@gmail.com on 11 Dec 2012 at 3:21

GoogleCodeExporter commented 9 years ago 
Loading a .so with the system loader after a memory error or SIGSEGV occurs 
seems dicey.  Couldn't you be inside malloc or the loader?

If you ignore stacks from signal handlers, then maybe the problem is easier.  
From signal handlers, it seems like the symbolizer has to be careful to avoid 
malloc.

Original comment by rnk@google.com on 11 Dec 2012 at 3:34

GoogleCodeExporter commented 9 years ago

Original comment by konstant...@gmail.com on 15 Feb 2013 at 2:28