https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #15 from Martin Liška ---
Okey, I really believe there's some ABI incompatibility between libsanitizer
and glibc. Maybe here:
https://github.com/gcc-mirror/gcc/blob/master/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc#L266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #14 from dominik.stras...@onespin-solutions.com ---
With the 9.0 version of libasan I also experience an additional crash which is
100% reproducible:
buffer points to non-accessible memory:
(gdb) p buffer
$1 = (__sanitizer::u64 *) 0x7f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #13 from dominik.stras...@onespin-solutions.com ---
The crash is not 100% reproducible. Looks like it is a race.
I'll check whether I can give you access to a system on our side.
I also encountered a differnt crash:
[Switching to Thr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #12 from dominik.stras...@onespin-solutions.com ---
Created attachment 45434
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45434&action=edit
Debug output in gdb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #11 from Martin Liška ---
(In reply to dominik.strasser from comment #10)
> Looking at the backtrace, the effects are very different between gcc 7.4 and
> 9.0. Making it work on a different glibc wouldn't help for me. CentOs 7.5 ==
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #10 from dominik.stras...@onespin-solutions.com ---
Looking at the backtrace, the effects are very different between gcc 7.4 and
9.0. Making it work on a different glibc wouldn't help for me. CentOs 7.5 ==
RHEL 7.5 which is the latest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #9 from Martin Liška ---
(In reply to dominik.strasser from comment #5)
> ASAN from git crashes like this. Looks like a double fault.
Yes, SEGFAULT happens right in the sanitizer code that's responsible
for creation of a thread. Thus
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #8 from Martin Liška ---
(In reply to dominik.strasser from comment #7)
> I canse it plays a role:
> I am running on a CentOS Linux release 7.5.1804
> which has kernel version 3.10.0-862.11.6.el7.x86_64
> and glibc glibc-2.17-222.el7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #7 from dominik.stras...@onespin-solutions.com ---
I canse it plays a role:
I am running on a CentOS Linux release 7.5.1804
which has kernel version 3.10.0-862.11.6.el7.x86_64
and glibc glibc-2.17-222.el7.i686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #6 from dominik.stras...@onespin-solutions.com ---
Created attachment 45426
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45426&action=edit
ASAN debug output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #5 from dominik.stras...@onespin-solutions.com ---
ASAN from git crashes like this. Looks like a double fault.
SignalHandler_Unix.h is in my application's code.
I've attached ASAN's debug output where I removed all messages talking abo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #4 from Martin Liška ---
(In reply to dominik.strasser from comment #3)
> Unfortunately my application is huge and spawns many threads.
>
> Can you propose some debugging aid. I am building gcc myself, so I can add
> anything to liba
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #3 from dominik.stras...@onespin-solutions.com ---
Unfortunately my application is huge and spawns many threads.
Can you propose some debugging aid. I am building gcc myself, so I can add
anything to libasan that you want.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #2 from Martin Liška ---
And please try GCC 8.2, maybe it has been fixed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
15 matches
Mail list logo