From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17570 invoked by alias); 10 Jun 2009 15:54:58 -0000 Received: (qmail 17559 invoked by uid 22791); 10 Jun 2009 15:54:56 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 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; Wed, 10 Jun 2009 15:54:49 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 5508A2BAAED for ; Wed, 10 Jun 2009 11:54:47 -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 ZT55UevwM8Pu for ; Wed, 10 Jun 2009 11:54:47 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 2D5B82BAAEA for ; Wed, 10 Jun 2009 11:54:47 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 90E05F596C; Wed, 10 Jun 2009 11:54:44 -0400 (EDT) Date: Wed, 10 Jun 2009 15:54:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: GDB BoF at the 2009 GCC Summit Message-ID: <20090610155444.GH25723@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00085.txt.bz2 Hello everyone, We hosted a GDB BoF at this year's GCC Summit, and the format we elected to use was a Q&A session, much like the Q&A session that we had for GCC. A few question were asked. I took a few notes, and just finished putting them on the Wiki: http://sourceware.org/gdb/wiki/2009_GCC_Summit_BoF (I also added a link from the main page of the Wiki). The couple of items that attracted my attention: - Are we going to move GDB to C++; - Status of the "inline" patch; - Debugging optimized code. We also received a few suggestions... -- Joel