From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24324 invoked by alias); 21 Dec 2012 06:05:52 -0000 Received: (qmail 24303 invoked by uid 22791); 21 Dec 2012 06:05:50 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,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; Fri, 21 Dec 2012 06:05:47 +0000 Received: from ([84.74.172.50]) by ms9smtp.webland.ch (Webland Mail Server v. 10.4.1) with ASMTP id FSA38444 for ; Fri, 21 Dec 2012 07:05:44 +0100 Received: from localhost (localhost [127.0.0.1]) by macserver.private (Postfix) with ESMTP id A30831516A34; Fri, 21 Dec 2012 07:05:42 +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 bDcaCdUHgawT; Fri, 21 Dec 2012 07:05:42 +0100 (CET) Received: from [192.168.1.83] (unknown [192.168.1.83]) by macserver.private (Postfix) with ESMTP id 023A51516A29 for ; Fri, 21 Dec 2012 07:05:41 +0100 (CET) Message-ID: <50D3FC31.1020103@indel.ch> Date: Fri, 21 Dec 2012 06:05:00 -0000 From: Raphael Zulliger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: gdb@sourceware.org Subject: Ensure correct symbol-file when attaching to a (remote) process 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: 2012-12/txt/msg00067.txt.bz2 Hi, I'm searching for a GDB feature that ensures that a symbol-file matches the running process to which I attach. More precisely, my use-case is that I attach to an already running embedded-system (bare metal) by extended-remote. Unfortunately, having a wrong ELF may result in showing wrong call stacks, etc. In worst case, you wont even notice that somethings wrong. I wasn't able to find something like that in the doc nor have I ever seen something like that in the remote serial protocol definition. Is there really no such mechanism in GDB? Raphael