From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14801 invoked by alias); 25 Feb 2008 13:55:04 -0000 Received: (qmail 14793 invoked by uid 22791); 25 Feb 2008 13:55:03 -0000 X-Spam-Check-By: sourceware.org Received: from ns.surtec.de (HELO SurTec.com) (62.157.175.70) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 25 Feb 2008 13:54:41 +0000 Received: from [192.168.1.5] (br.surtec.com [200.161.1.30]) by SurTec.com (Postfix) with ESMTP id B93CB20B9D1 for ; Mon, 25 Feb 2008 14:54:38 +0100 (CET) Message-Id: <4DD16CA6-AF98-4599-A9F5-CAF0EA4F3E84@surtec.com> From: "Dr. Rolf Jansen" To: gdb@sourceware.org In-Reply-To: <20080225133150.GB19361@caradoc.them.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: Using dlopen and remote debugging Date: Mon, 25 Feb 2008 14:23:00 -0000 References: <1015843957@web.de> <92BB1E0C-6CEC-41FF-AD60-A7F2590D1DA1@surtec.com> <20080225133150.GB19361@caradoc.them.org> X-Mailer: Apple Mail (2.919.2) 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: 2008-02/txt/msg00212.txt.bz2 Am 25.02.2008 um 10:31 schrieb Daniel Jacobowitz: > On Mon, Feb 25, 2008 at 10:03:09AM -0300, Dr. Rolf Jansen wrote: > >> In my case this was impossible. The remote machine happened to run >> Windows XP and the host Mac OS X. I found no way to let Mac OS X >> understand a full path like "C:\path\to\my\exe\and\dll. I needed to >> patch >> gdbserver. In the latest CVS version I changed server.c beginning >> at line >> 528 to: > > Then just set solib-search-path; GDB will look up the basenames. I did this to no avail. > There is an additional wrinkle involving path separators, since GDB > is likely to think that is bare filename and not a full path. Yeah, as I said, the host gdb at the Mac does not understand the path semantics that is send from gdbserver at Windows. > But it should be fixed on the GDB side, not on the target side. I am comfortable with that - fix it however and whenever you want! Once it is fixed, I will abandon my quick hack. Until that I have a working solution. > This one's been discussed a few times recently. Discussions are good, solutions are better - even quick 'n dirty ones. Rolf