From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14719 invoked by alias); 29 Jan 2013 03:18:28 -0000 Received: (qmail 14479 invoked by uid 22791); 29 Jan 2013 03:18:24 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from ms9.webland.ch (HELO ms9smtp.webland.ch) (92.43.217.109) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 29 Jan 2013 03:18:20 +0000 Received: from ([84.74.172.50]) by ms9smtp.webland.ch (Webland Mail Server v. 10.4.1) with ASMTP id OEV64716; Tue, 29 Jan 2013 04:18:16 +0100 Received: from localhost (localhost [127.0.0.1]) by macserver.private (Postfix) with ESMTP id 215CB1597A25; Tue, 29 Jan 2013 04:18:15 +0100 (CET) Received: from macserver.private ([127.0.0.1]) by localhost (macserver.private [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsCZB5e0tSPP; Tue, 29 Jan 2013 04:18:14 +0100 (CET) Received: from [192.168.1.83] (unknown [192.168.1.83]) by macserver.private (Postfix) with ESMTP id B53211597A1A; Tue, 29 Jan 2013 04:18:14 +0100 (CET) Message-ID: <51073F73.5000905@indel.ch> Date: Tue, 29 Jan 2013 03:18:00 -0000 From: Raphael Zulliger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pedro Alves CC: gdb@sourceware.org Subject: Re: Ensure correct symbol-file when attaching to a (remote) process References: <50D3FC31.1020103@indel.ch> <20121221161114.GA32638@host2.jankratochvil.net> <201212211917.qBLJH6Il028006@new.toad.com> <50E474E3.7050605@redhat.com> In-Reply-To: <50E474E3.7050605@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2013-01/txt/msg00080.txt.bz2 (I apologize: I've replied to this mail some weeks ago - but forgot to CC to the list. I therefore resend this email) On 01/02/2013 06:56 PM, Pedro Alves wrote: > A build id check would really be ideal. I agree. (--build-id is a very interesting feature which I was not aware of. Thanks for that hint Jan) In our scenario, our GDB stub could get that build-id from the running target: Our embedded systems provides a variable read/write mechanism accessible by the stub. Moreover, the embedded system could be made aware of the address of the build-id by introducing variables around the .note.gnu.build-id section in the linker script. Therefore, if the GDB remote serial protocol would offer a way to "get" that id from the stub and GDB would offer a feature to compare/check that id, it'd perfectly work for us. AFAIK there are no "generic" ways of transferring data by the remote serial protocol, therefore, we'd need to extend it accordingly, right? Could such a protocol extension, and the according build-id comparison check make it into GDB?