This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/60536] Backtrace corrupted on Firefox build with -fsanitize=address and -flto
- From: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 17 Mar 2014 08:53:38 +0000
- Subject: [Bug sanitizer/60536] Backtrace corrupted on Firefox build with -fsanitize=address and -flto
- Auto-submitted: auto-generated
- References: <bug-60536-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60536
--- Comment #12 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Kostya Serebryany from comment #11)
> > Sorry, but I don't have a google account and refuse to create one.
> You can login to our bug tracker with any existing e-mail,
> or you can contact us via address-sanitizer@googlegroups.com
> or you can file a bug using the llvm bug tracker
OK, sorry. I didn't know that.
(In reply to Kostya Serebryany from comment #10)
> > ==10632==ERROR: AddressSanitizer: heap-use-after-free on address
> > 0x60200001ec50 at pc 0x7f3e30645dbd bp 0x7fff6d3b2a60 sp 0x7fff6d3b2a38
> > READ of size 2 at 0x60200001ec50 thread T0
> > #0 0x7f3e30645dbc in setlocale
>
> So, sounds like a real use-after-free in firefox
No. It's a bug in libqtcurve (a QT/GTK theme). When I switch to a different
theme I hit the real Firefox bug that I was after:
https://bugzilla.mozilla.org/show_bug.cgi?id=983995
What about the "allocating memory until the OOM killer hits" issue?
Do you think this is an asan bug?