From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13288 invoked by alias); 24 Feb 2009 17:08:59 -0000 Received: (qmail 13278 invoked by uid 22791); 24 Feb 2009 17:08:58 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Feb 2009 17:08:53 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 6A374105BB; Tue, 24 Feb 2009 17:08:51 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 343C71018B; Tue, 24 Feb 2009 17:08:51 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Lc0m2-0003pu-Jp; Tue, 24 Feb 2009 12:08:50 -0500 Date: Tue, 24 Feb 2009 17:08:00 -0000 From: Daniel Jacobowitz To: Brendan Miller Cc: gdb@sourceware.org Subject: Re: problem remote debugging Message-ID: <20090224170850.GA14727@caradoc.them.org> Mail-Followup-To: Brendan Miller , gdb@sourceware.org References: <20090224023251.GA22085@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2009-02/txt/msg00150.txt.bz2 On Tue, Feb 24, 2009 at 09:01:11AM -0800, Brendan Miller wrote: > I'm not sure if that makes sense. What happened was a file failed to > be read, which to me implies different behavior given the same > binaries executed on the same machine, depending on if in local or > remote debugging mode. This was followed by a segfault which may or > may not be related. I can see how the gdb client would crash if I > didn't have the proper debugging symbols on the client, but could that > really effect other behavior on the remote machine? Yes, really. I've just tried to explain this... GDB sets breakpoints in the target automatically, and reads debug data from the target. If symbols do not match, then it will set the breakpoints at the wrong location (which might even be data rather than code), and it will read incorrect debug information and make decisions based on that. > > Also, this is a very old GDB - I always recommend trying the latest > > (GDB and gdbserver). > > Is there a known bug that was fixed that would resolve this? Well, for one thing it'll try to warn you if your libraries don't match. -- Daniel Jacobowitz CodeSourcery