Closed GoogleCodeExporter closed 9 years ago
This line suggests that the program tries to copy something to NULL address:
__interceptor_memcpy (dst=0x0, src=src@entry=0x7d8000015000,
size=size@entry=128)
which is expected to crash.
Please double check that the program itself is not buggy.
If you run it with -fsanitize=address, what is the output?
Original comment by dvyu...@google.com
on 26 Apr 2014 at 11:47
I've been running it under address sanitizer for quite some time and there are
no errors (unfortunately, I do believe there is a bug in the program somewhere
as it sporadically results in glMapBuffer() failure -- but it happens very
rarely and I couldn't pinpoint it yet). Moreover, the line in the stack trace
#12 is literally just
glClear(GL_COLOR_BUFFER_BIT);
Perhaps there is something wrong inside Mesa GL driver, but this is,
unfortunately outside of my control, so I'd like to blacklist it if I could,
but I don't see any way to prevent this crash from happening...
Original comment by vzeitlin@gmail.com
on 26 Apr 2014 at 12:10
ThreadSanitizer can significantly disturb timings and cause the bug to happen
much more frequently.
I can suggest to nsert printf before the memcpy call, to verify NULL
hypothesis. If it's just a bug in mesa, then there is not much we can do.
You can also try with clang tip instead of gcc (here are build instructions
https://code.google.com/p/address-sanitizer/wiki/HowToBuild) maybe it will
affect something (or maybe a clang compilation warning will point you to the
bug).
Original comment by dvyu...@google.com
on 26 Apr 2014 at 12:22
Just to be clear: with TSAN, it's not a timing problem, the crash happens
immediately on startup, i.e. on the very first call to glClear().
I might try it with clang later but for now I managed to finally get something
from valgrind so I'm going to investigate this first...
Original comment by vzeitlin@gmail.com
on 26 Apr 2014 at 12:50
I will appreciate if you report back with your findings. If it's a bug in tsan,
I would like to fix it.
Original comment by dvyu...@google.com
on 27 Apr 2014 at 10:08
Closing, but you still can report your findings here.
Original comment by dvyu...@google.com
on 7 May 2014 at 8:59
Original issue reported on code.google.com by
vzeitlin@gmail.com
on 26 Apr 2014 at 11:38