This is an env variable ASAN_OPTIONS= allocator_may_return_null=1
On Mar 15, 2014 9:49 PM, "Jeffrey Walton" wrote:
> I ==26311==WARNING: AddressSanitizer failed to allocate 0x7fff
> bytes
> ==26311==AddressSanitizer's allocator is terminating the process
> instead of returning 0
> ==2
I ==26311==WARNING: AddressSanitizer failed to allocate 0x7fff bytes
==26311==AddressSanitizer's allocator is terminating the process
instead of returning 0
==26311==If you don't like this behavior set allocator_may_return_null=1
Is this allocator_may_return_null and environmental vari
On Sat, Mar 15, 2014 at 7:47 PM, Jeffrey Walton wrote:
> Python is brutal for someone who does not know it (I'm a C/C++/ObjC
> guy). I'm amazed that basic functionality such as print was broken
> between 2 & 3. Imagine if printf stopped working in C99!
Oh, don't get me started. After years of Pyt
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 275 by noloa...@gmail.com: asan_symbolize.py does not work with
Python3
http://code.google.com/p/address-sanitizer/issues/detail?id=275
The fix appears to be very easy: add parenthesis around arguments
to 'print'.
Its p
On Sat, Mar 15, 2014 at 11:40 AM, Yuri Gribov wrote:
> I believe llvm_symbolizer expects python2 interpreter. You could try
> one of these
> * install your Python 3 as /usr/local/bin/python3 to avoid shadowing
> default system Python
> * explicitly run llvm_symbolizer under Python2 interpreter
> *
I believe llvm_symbolizer expects python2 interpreter. You could try
one of these
* install your Python 3 as /usr/local/bin/python3 to avoid shadowing
default system Python
* explicitly run llvm_symbolizer under Python2 interpreter
* update asan_symbolizer.py using 2to3
-Y
--
You received this m
> Thanks for the help.
Np, glad to help.
-Y
--
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 address-sanitizer+unsubscr...@googlegroups.com.
For more optio
On Sat, Mar 15, 2014 at 12:32 PM, Konstantin Serebryany
wrote:
> We see the stack trace from asan's SEGV handler, so __asan_init was already
> called.
True, I wonder what could go wrong then?
-Y
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer"
On Sat, Mar 15, 2014 at 10:50 AM, Alexander Potapenko
wrote:
> Which Python version are you using?
$ python --version
Python 3.3.5
$ which python
/usr/local/bin/python
It was built from sources because I needed SSL's server name
indication (SNI) of Python 3.x. The version installed in
/usr/local
Which Python version are you using?
What happens if you invoke the script as 'python asan_symbolize.py'?
You'll also need to redirect stderr into stdout (2>&1), because ASan prints
the reports into stderr.
On Mar 15, 2014 6:17 PM, wrote:
> Hi Gentleman,
>
> I managed to get myself in more troubl
Hi Gentleman,
I managed to get myself in more trouble. This time with asan_symbolize.py.
$ make | asan_symbolize.py
File "/usr/local/bin/asan_symbolize.py", line 69
print ' '.join(cmd)
^
SyntaxError: invalid syntax
Here's the relevant snippet:
def open_llvm_symbolizer(self)
On Saturday, March 15, 2014 3:36:25 AM UTC-4, Yuri Gribov wrote:
>
> > Does
> > anyone have an idea why PC is 0x?
>
> I think that Asan initialization code (__asan_init) didn't run so
> glibc interceptors were not set up.
>
> > The only un-ordinary
> > part was I had to add some of t
On Saturday, March 15, 2014 3:36:25 AM UTC-4, Yuri Gribov wrote:
>
> > Does
> > anyone have an idea why PC is 0x?
>
> I think that Asan initialization code (__asan_init) didn't run so
> glibc interceptors were not set up.
>
> > The only un-ordinary
> > part was I had to add some of t
On Sat, Mar 15, 2014 at 11:36 AM, Yuri Gribov wrote:
> > Does
> > anyone have an idea why PC is 0x?
>
> I think that Asan initialization code (__asan_init) didn't run so
> glibc interceptors were not set up.
>
> > The only un-ordinary
> > part was I had to add some of the sanitizer librar
> Does
> anyone have an idea why PC is 0x?
I think that Asan initialization code (__asan_init) didn't run so
glibc interceptors were not set up.
> The only un-ordinary
> part was I had to add some of the sanitizer libraries to LIBS due to
> undefined symbols like __asan_report8 when build
15 matches
Mail list logo
