https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #19 from Maxim Ostapenko ---
Should be fixed now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #18 from Maxim Ostapenko ---
Author: chefmax
Date: Wed Jan 13 09:27:38 2016
New Revision: 232316
URL: https://gcc.gnu.org/viewcvs?rev=232316&root=gcc&view=rev
Log:
Cherry-pick r224315 and r241487 from upstream.
PR sanitizer/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #17 from Dominique d'Humieres ---
Results with the third patch at
https://gcc.gnu.org/ml/gcc-testresults/2016-01/msg01115.html
It looks good.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #16 from Dominique d'Humieres ---
Looks good on preliminary testing. Full regtesting in progress.
> Le 12 janv. 2016 à 16:52, chefmax at gcc dot gnu.org
> a écrit :
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
>
> --- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #15 from Maxim Ostapenko ---
Created attachment 37316
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37316&action=edit
Third attempt.
Eh, it seems that I missed one another commit from upstream that needed to be
backported, sor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #14 from Dominique d'Humieres ---
> Le 12 janv. 2016 à 13:55, chefmax at gcc dot gnu.org
> a écrit :
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
>
> --- Comment #13 from Maxim Ostapenko ---
> Created attachment 37313
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #13 from Maxim Ostapenko ---
Created attachment 37313
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37313&action=edit
Second fix.
My bad, could you try this one?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #12 from Dominique d'Humieres ---
> Upstream ASan already has the fix, attaching adapted cherry-picked commit.
> Could you try it?
Bootstrapping with this patch fails with
...
../../../../5_work/libsanitizer/asan/asan_mac.cc
libtoo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #11 from Dominique d'Humieres ---
> Upstream ASan already has the fix, attaching adapted cherry-picked commit.
> Could you try it?
My machine is currently bootstrapping the trunk. It should finish in an hour or
so. I'll test your pat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #10 from Maxim Ostapenko ---
Created attachment 37310
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37310&action=edit
Proposed fix.
« El Capitan » is OS X 10.11, right? So, this is my vision of the problem:
In OS X 10.11+ or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #9 from Dominique d'Humieres ---
> Le 12 janv. 2016 à 10:11, chefmax at gcc dot gnu.org
> a écrit :
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
>
> --- Comment #8 from Maxim Ostapenko ---
> Eh, this is sad, let's try m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #8 from Maxim Ostapenko ---
Eh, this is sad, let's try more. I suspect that ASan fails in MaybeReexec
function (it tries to set DYLD_INSERT_LIBRARIES env variable and reexec
itself). Dominique can I ask you two questions:
1) I'm not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #7 from Dominique d'Humieres ---
I have run memcmp-1.exe under lldb trying various break points from line 1 to
12 and I always get
Process 45744 launched:
'/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/memcmp-1.exe' (x86_64)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #6 from Maxim Ostapenko ---
Ok, it seems that libasan calls some function to be intercepted while
AsanInitInternal still not completed. Could you try to run memcmp-1.exe under
gdb to provide a backtrace from failed CHECK? This way, we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #4 from Maxim Ostapenko ---
If you want use make check stuff, you could try this:
max:~/build/master> setenv ASAN_OPTIONS verbosity=2:debug=1
max:~/build/master> make check RUNTESTFLAGS="asan.exp=memcmp-1.c"
or add such a line to, s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #3 from Dominique d'Humieres ---
Could you please elaborate?
Is there a way to run manually a test with ASAN_OPTIONS=debug=1:verbosity=2? If
yes, how (I am using tcsh)?
If no, can I do it at the test love? If yes, how? If no, I guess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
--- Comment #2 from Maxim Ostapenko ---
Dominique, could you please run ASan tests with
ASAN_OPTIONS=debug=1:verbosity=2? This might be helpful for further debugging.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
Yury Gribov changed:
What|Removed |Added
CC||chefmax at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69147
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |5.4
21 matches
Mail list logo
