This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] fullname attribute for GDB/MI stack frames
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Dennis Brueni <dbrueni at slickedit dot com>, gdb-patches at sources dot redhat dot com
- Date: Sun, 01 May 2005 21:22:31 +0300
- Subject: Re: [RFC] fullname attribute for GDB/MI stack frames
- References: <ECCC6E9907B4CD4A83260A191A91F20E22C6D2@wampa.office.slickedit.com> <20050430191755.GF7009@nevyn.them.org> <20050501021945.GA19962@white>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 30 Apr 2005 22:19:45 -0400
> From: Bob Rossi <bob@brasko.net>
>
> On Sat, Apr 30, 2005 at 03:17:55PM -0400, Daniel Jacobowitz wrote:
> > On Fri, Apr 01, 2005 at 02:13:33PM -0500, Dennis Brueni wrote:
> > > > Again, for the fullname regex, I would recommend using the
> > > > same regex used in mi-file.exp. This would be like
> > > > fullname="/.*basics.c" This forces the regex to ensure that
> > > > the path is absolute, which the check you have does not.
> >
> > Will GDB always output absolute paths that start with "/"? What about
> > non-Cygwin Windows for example? DJGPP?
To answer Daniel's question: no, absolute file names on DOS/Windows
systems do not necessarily begin with a slash.
> Like Dennis noted, it could be possible that the fullname might not
> start with a "/". I originally posted the patch with the fullname
> starting with a "/", and since then, there hasn't been any complaints.
> If there is a better regex that ensures that the fullname is absolute
> I'd be happy to change the mi-file.exp test to it.
The proper regexp should be something like
\([A-z]:\)?[/\\].*basics.c
This assumes that \(...\) is the proper syntax for grouping (I don't
know much about the regexp syntax expected by Expect).
(The uppercase A but lowercase z in the above are intentional: that's
because letters between Z and a can also be drive letters, amazingly
enough.)