Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
Target Milestone: ---
This is new on gcc 9.
# cat array_bounds.c
struct trace_iterator {
char a;
int seq;
long b;
};
void f(void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210
--- Comment #2 from Andrey Ryabinin ---
(In reply to Richard Biener from comment #1)
> Confirmed. Note that I'm not sure it makes no sense - it just means the
> function has no side-effect besides not returning ;)
>
Well, GCC docs say that
: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at
gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81040
--- Comment #15 from Andrey Ryabinin ---
(In reply to Martin Liška from comment #14)
> Fixed on trunk.
Thanks.
However there is slight problem with this. Instrumentation is missing without
-fsanitize-address-use-after-scope option.
IMO, it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81040
--- Comment #7 from Andrey Ryabinin ---
(In reply to Martin Liška from comment #6)
> Can't see that clang++ is capable of catching your first test-case:
>
> $ clang++ pr81040.cpp -fsanitize=address && ./a.out
> pr81040.cpp:3:9: warning:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81040
--- Comment #4 from Andrey Ryabinin ---
(In reply to Martin Liška from comment #3)
> As mentioned by Richard, currently ASAN is able to protect function
> variables that live on stack. In your case the function foo is called with
> constant that
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67513
--- Comment #4 from Andrey Ryabinin ---
(In reply to Andrey Ryabinin from comment #3)
> (In reply to Yury Gribov from comment #1)
> > (In reply to Andrey Ryabinin from comment #0)
> > > (shadow value is usually zero).
> >
> > What makes you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67513
--- Comment #3 from Andrey Ryabinin ---
(In reply to Yury Gribov from comment #1)
> (In reply to Andrey Ryabinin from comment #0)
> > (shadow value is usually zero).
>
> What makes you think so? AFAIU for less-than-8-byte scalars it's always
>
: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67368
Andrey Ryabinin changed:
What|Removed |Added
CC||ryabinin.a.a at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63802
Andrey Ryabinin ryabinin.a.a at gmail dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: ryabinin.a.a at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61848
--- Comment #8 from Andrey Ryabinin ryabinin.a.a at gmail dot com ---
Hi, may I ask what's the status of this?
Besides of section mismatches in linux kernel it also breaks kernel's modules.
Variable __this_module doesn't get into section
15 matches
Mail list logo
