From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13725 invoked by alias); 5 Jul 2011 17:08:00 -0000 Received: (qmail 13708 invoked by uid 22791); 5 Jul 2011 17:07:59 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_LV X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Jul 2011 17:07:36 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 7BF272BAF9B; Tue, 5 Jul 2011 13:07:35 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4j-98FNjRffd; Tue, 5 Jul 2011 13:07:35 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 75A702BAF82; Tue, 5 Jul 2011 13:07:34 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id AA2A0145615; Tue, 5 Jul 2011 10:07:28 -0700 (PDT) Date: Tue, 05 Jul 2011 17:44:00 -0000 From: Joel Brobecker To: Paul Pluzhnikov Cc: Jan Kratochvil , gdb-patches@sourceware.org, Yuri Subject: Re: [patch,7.3] Fix JIT clang-lli gdb-7.3 regression Re: [gdb-7.3] Error in gdb-llvm integration: Unable to read JIT descriptor from remote memory! Message-ID: <20110705170728.GY2407@adacore.com> References: <4E0FAB8D.2070709@rawbw.com> <20110704214654.GA21844@host1.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00160.txt.bz2 Jan, Paul, We're getting ready to produce the first gdb-7.3 candidate release, and we're thinking of either: - going with Jan's patch for now, with a view of possibly making it better with a followup patch if necessary; - releasing 7.3 with JIT as a known problem, hopefully to be fixed for 7.3.1, depending on how safe the fix is perceived. Either way, we'd like to issue the pre-release either tomorrow, of Thu if Jan doesn't come back tomorrow. And if all goes well, and no blocking bug is found, the 7.3 official release would be created 2 weeks later. -- Joel