From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15263 invoked by alias); 16 Dec 2003 00:10:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15250 invoked from network); 16 Dec 2003 00:10:42 -0000 Received: from unknown (HELO lakemtao03.cox.net) (68.1.17.242) by sources.redhat.com with SMTP; 16 Dec 2003 00:10:42 -0000 Received: from white ([68.9.64.121]) by lakemtao03.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031216001040.XGV2192.lakemtao03.cox.net@white> for ; Mon, 15 Dec 2003 19:10:40 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1AW2nQ-00023U-00 for ; Mon, 15 Dec 2003 19:10:40 -0500 Date: Tue, 16 Dec 2003 00:10:00 -0000 From: Bob Rossi To: gdb@sources.redhat.com Subject: -file-list-exec-source-files implementation Message-ID: <20031216001040.GA7871@white> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-SW-Source: 2003-12/txt/msg00229.txt.bz2 Hi, I am working on implementing the -file-list-exec-source-files command for the MI interface. I wanted to make sure the community liked my ideas before I really got into it. I looked at sources_info in symtab.c to find out how to implement the MI call. The only change I think would be nice over the CLI interface is if the MI command gave the fullpath along with the regular path that 'info sources' currently outputs. I currently have come up with 3 possibilities and wonder what's best. 1. I could make -file-list-exec-source-files always return the fullpath. 2. I could make -file-list-exec-source-files return the fullpath of each file if a parameter was passed to the function. The obvious question with these 2 option's is if finding the fullpath for each file is to costly of an operation to put upon each user of this function. 3. The other option is to do it the way the CLI does it. It makes the user do the 'info sources' to find the file of interest. And then do 'list foo.c:1' and then 'info source'. After that, the CLI outputs the absolute path to the file foo.c. I could make the user do '-file-list-exec-source-files' to get the relative paths. Then the user could do '-file-list-exec-source-file foo.c' to get the absolute path to that file. I prefer the first alternative if it is possible to look up the fullpath to all of the file's that the exe is made up of. This must be scalable for even the largest executable's that GDB supports. Does this sound reasonable? I don't really know how costly the operation of looking up the fullpath to a file is in GDB. If it is not reasonable, the third alternative will be the best way to go. Any suggestions? Thanks, Bob Rossi