public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gk at torproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/61408] r205695 breaks packaging step of Firefox 24 ESR on Ubuntu Lucid building with ASan
Date: Wed, 04 Jun 2014 13:39:00 -0000	[thread overview]
Message-ID: <bug-61408-4-jwKE7h0uvf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61408-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61408

--- Comment #5 from Georg Koppen <gk at torproject dot org> ---
(In reply to Kostya Serebryany from comment #4)
> > > LLVM trunk?
> > 
> > Have not tried yet. Shall I?
> 
> asan is being developed in LLVM trunk.
> So if there is a bug in run-time it's better to investigate the freshest
> variant in LLVM trunk
> The fix will have to go there first anyway.

Okay. Then I'll do that. Note that the last crash is happening on my Precise
system as well now. Thus, I guess this is a different issue worth another bug.
Anyway, I'll post back when I have convinced LLVM/Clang to compile Firefox.


  parent reply	other threads:[~2014-06-04 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  5:56 [Bug sanitizer/61408] New: " gk at torproject dot org
2014-06-04  5:57 ` [Bug sanitizer/61408] " gk at torproject dot org
2014-06-04  7:22 ` kcc at gcc dot gnu.org
2014-06-04 10:33 ` gk at torproject dot org
2014-06-04 10:51 ` kcc at gcc dot gnu.org
2014-06-04 13:39 ` gk at torproject dot org [this message]
2014-06-04 13:42 ` jakub at gcc dot gnu.org
2014-06-05 13:10 ` gk at torproject dot org
2014-06-09 15:01 ` gk at torproject dot org
2014-06-11 12:45 ` gk at torproject dot org
2014-06-11 19:06 ` gk at torproject dot org
2014-06-16 10:51 ` gk at torproject dot org
2014-06-16 11:24 ` kcc at gcc dot gnu.org
2014-06-16 11:29 ` gk at torproject dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-61408-4-jwKE7h0uvf@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).