From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19564 invoked by alias); 5 May 2005 15:15:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19360 invoked from network); 5 May 2005 15:15:03 -0000 Received: from unknown (HELO wampa.office.slickedit.com) (24.106.178.205) by sourceware.org with SMTP; 5 May 2005 15:15:03 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: [RFC] fullname attribute for GDB/MI stack frames Date: Thu, 05 May 2005 15:15:00 -0000 Message-ID: From: "Dennis Brueni" To: Cc: "Dennis Brueni" , "Bob Rossi" X-SW-Source: 2005-05/txt/msg00160.txt.bz2 On Wed, 4 May 2005 20:05:06 -0400, Bob Rossi wrote: >=20 > This may or may not be what you mean. However, if you do > -file-list-exec-source-files, GDB prints the filename and fullname for > every file that it knows about. The purpose of this is to let the front > end know about each and every file that GDB knows about. As I've stated > before, I believe most if not all FE's depend on the fullname to be a > unique key. I think you have just struck on the right way to write the tests for fullname with respect to stack frames. Forget regex's, we want the value of the fullname to exactly match the same fullname attribute pumped out by -file-list-exec-source-files. This would just take one utility function. The test for -file-list-exec-source-files could then be the central point for verifying the "correctness" of fullname. I'm willing to redo my stack/fullname tests if this idea is amenable to the group. --Dennis ------------------------ Dennis Brueni Software Engineer SlickEdit Inc. 3000 Aerial Center Pkwy Suite 120 Morrisville, NC 27560 Tel: 919.473.0132 Fax: 919.473.0080 http://www.slickedit.com ------------------------=20=20=20=20=20=20=20