From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28479 invoked by alias); 24 Jun 2006 13:08:45 -0000 Received: (qmail 28428 invoked by uid 22791); 24 Jun 2006 13:08:44 -0000 X-Spam-Check-By: sourceware.org Received: from sadr.equallogic.com (HELO sadr.equallogic.com) (66.155.203.134) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 24 Jun 2006 13:08:41 +0000 Received: from sadr.equallogic.com (localhost.localdomain [127.0.0.1]) by sadr.equallogic.com (8.12.8/8.12.8) with ESMTP id k5OD8cUQ009787 for ; Sat, 24 Jun 2006 09:08:39 -0400 Received: from M31.equallogic.com (M31.equallogic.com [172.16.1.31]) by sadr.equallogic.com (8.12.8/8.12.8) with SMTP id k5OD8cce009782; Sat, 24 Jun 2006 09:08:38 -0400 Received: from PKONING.equallogic.com ([172.16.3.123]) by M31.equallogic.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 24 Jun 2006 09:08:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17565.14669.328000.544685@gargle.gargle.HOWL> Date: Sat, 24 Jun 2006 13:27:00 -0000 From: Paul Koning To: brobecker@adacore.com Cc: gdb@sources.redhat.com Subject: Re: Should "dir" override the full path encoded in debug info? References: <20060623201019.GX22750@adacore.com> <20060623201839.GA2920@nevyn.them.org> <20060624070842.GC22750@adacore.com> X-Mailer: VM 7.07 under 21.4 (patch 10) "Military Intelligence (Windows)" XEmacs Lucid X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00211.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: >> It is quite likely that what you really want is not "dir", but >> this: >> >> http://sourceware.org/ml/gdb/2006-03/msg00189.html >> >> Hey, Paul... Joel> Indeed, that would solve the proble entirely. I wonder how this Joel> should be implemented... Should the command store the rewriting Joel> rule, and have find_and_open_source() use it when trying to Joel> locate source files? I forgot where I put it. What I did is a simple rewriting rule -- a command with two string arguments, where one is the string to find in the filenames and the other the replacement string. A fancier solution would have multiple substitution pairs, and/or regular expressions. For our purposes, one pair with simple strings was sufficient. Once I get out from my current time crunch I'll see about digging up the change and submitting it as a proposed patch. paul