From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12240 invoked by alias); 14 Feb 2012 15:47:06 -0000 Received: (qmail 12225 invoked by uid 22791); 14 Feb 2012 15:47:04 -0000 X-SWARE-Spam-Status: No, hits=-2.0 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; Tue, 14 Feb 2012 15:46:39 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 2F4AE1C6566; Tue, 14 Feb 2012 10:46:39 -0500 (EST) 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 6hKl8C3Cvl+r; Tue, 14 Feb 2012 10:46:39 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id EDAB11C6538; Tue, 14 Feb 2012 10:46:38 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 2E6A0145615; Tue, 14 Feb 2012 19:46:34 +0400 (RET) Date: Tue, 14 Feb 2012 15:47:00 -0000 From: Joel Brobecker To: Tristan Gingold Cc: "gdb-patches@sourceware.org ml" Subject: Re: RFA: [Ada] extract known tasks array parameters from symbol table Message-ID: <20120214154634.GA14803@adacore.com> References: <7A06C670-A574-4AE4-A89C-2532671E5F64@adacore.com> <20120213161529.GE3474@adacore.com> 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: 2012-02/txt/msg00269.txt.bz2 > > The problem is that certain GNU/Linux distributions decided to simply > > strip all runtime libraries of debug info, and then provide additional > > packages for the debug version of these shared libs. And apparently, > > it's a significant disruption to address this issue at the package > > creation level. So we need to try to support those users the best > > we can. > > Ok. But how are debug infos for the ATCB read ? Are they in the > executable due to implicit with of ada.tasking ? I am not 100% sure, but that's my guess as well. -- Joel