[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #5 from Jakub Jelinek jakub at gcc dot gnu.org --- BTW, the second line change in the function heuristics also fails for say: #include stdarg.h void bar (va_list ap); void foo (int a, ...) { va_list ap; va_start (ap, a); bar

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jan.kratochvil at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #6 from Jan Kratochvil jan.kratochvil at redhat dot com --- (In reply to Jakub Jelinek from comment #5) as in the case of the varargs x86_64 function that might need saving xmm registers, [...] So, does GDB have a disassemble

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added CC||drow at gcc dot

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jan.kratochvil at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #8 from Jan Kratochvil jan.kratochvil at redhat dot com --- Typo above, the real GDB commit of the XMM registers init workaround was:

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jan.kratochvil at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #9 from Jan Kratochvil jan.kratochvil at redhat dot com --- Confirming x86_64-linux testsuite on gdb-7.7.50.20140218-cvs has no changes/regressions. (Also confirming it fixes for me the Comment 0 gcc4.9 regression.)

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #10 from Jakub Jelinek jakub at gcc dot gnu.org --- Author: jakub Date: Tue Feb 18 21:16:21 2014 New Revision: 207853 URL: http://gcc.gnu.org/viewcvs?rev=207853root=gccview=rev Log: PR sanitizer/60142 * final.c (SEEN_BB):

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-18 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-12 Thread jan.kratochvil at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 Jan Kratochvil jan.kratochvil at redhat dot com changed: What|Removed |Added CC|

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-11 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 Richard Biener rguenth at gcc dot gnu.org changed: What|Removed |Added Keywords||wrong-debug

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-11 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added CC||jkratoch at gcc

[Bug sanitizer/60142] [4.9 Regression][asan] -fsanitize=address breaks debugging - stepping into functions no longer possible

2014-02-11 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60142 --- Comment #3 from Tobias Burnus burnus at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #2) Works also with [...] or -O0 -fsanitize=address -g --param asan-use-after-return=0. For what it is worth and with that comment rather