Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: David Carlton <carlton@math.stanford.edu>,
	gdb <gdb@sources.redhat.com>, Andrew Cagney <ac131313@redhat.com>
Subject: Re: bug in gdb.mi/mi-file.exp (or maybe in GDB)
Date: Wed, 09 Apr 2003 21:28:00 -0000	[thread overview]
Message-ID: <20030409212815.GC22063@white> (raw)
In-Reply-To: <16020.36832.631285.111407@localhost.redhat.com>

On Wed, Apr 09, 2003 at 05:25:52PM -0400, Elena Zannoni wrote:
> David Carlton writes:
>  > On Wed, 9 Apr 2003 16:30:24 -0400, Bob Rossi <bob_rossi@cox.net> said:
>  > > On Wed, Apr 09, 2003 at 01:01:41PM -0700, David Carlton wrote:
>  > 
>  > >> gdb.log says:
>  > >> 
>  > >> 111^done,line="23",file="gdb.mi/basics.c",fullname="/extra/gdb/mirror/src/gdb/testsuite/gdb.mi/basics.c"
>  > 
>  > > This is what I get, which passes
>  > > 111^done,line="23",file="./gdb.mi/basics.c",fullname="/home/bob/cvs/src/gdb/testsuite/gdb.mi/basics.c"^
>  > 
>  > Ah. I guess maybe different versions of GCC differ as to whether or
>  > not they include the './' in the filename in the debug info, or
>  > something.
>  > 
> 
> Compiling and building everything with absolute paths in build!=src, I
> get absolute paths in both.
> 
> 111^done,line="23",file="/home/ezannoni/sources/src/gdb/testsuite/gdb.mi/basics.c",fullname="/home/ezannoni/sources/src/gdb/testsuite/gdb.mi/basics.c"
> 
>  > >> Should 'file' match .*${srcfile}
>  > >> (without any slashes) and 'fullname' match ${srcfilepath}?
>  > 
>  > > I think your suggestion of what file should match is a good one.
>  > 
>  > Elena just raised a similar issue in annota1.exp.  So maybe we should
>  > wait for the resolution there and then adopt the same solution for
>  > 'file' here.  (Though the format of 'file' is less crucial here, since
>  > that's what 'fullname' is for.)
>  >  
> 
> All I care about it to match correctly with '+' in the directory
> names. So maybe all I need is to use string_to_regexp and leave the
> full path in there.
> 
>  > > The fullname match should probably not change. Since ${srcfilepath}
>  > > is not guaranteed to be the absolute path to the source file.
>  > 
>  > Oh, right, duh.  I should have tested that before suggesting it!
>  > 
> 
> Ah right, ${srcfilepath} is set up by the testsuite machinery, not
> gdb, so it is not guaranteed to match fullname.  I thought you meant
> that fullname could not be absolute, and that got me puzzled.  Bottom
> line, the testsuite doesn't know what the absolute path is.  We could
> pull the dirty trick of asking gdb for it, with an 'info source' and
> use that output to match.

I think if we did that, they might break consistently, and the test case
could still pass. It seems like maybe we should allow the file to match
the same thing we allow fullname to match. "/.*$(srcfile}" Since it is legal.

Bob Rossi

> 
> 
> elena
> 
> 
>  > David Carlton
>  > carlton@math.stanford.edu


  reply	other threads:[~2003-04-09 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 20:01 David Carlton
2003-04-09 20:30 ` Bob Rossi
2003-04-09 20:38   ` David Carlton
2003-04-09 21:21     ` Elena Zannoni
2003-04-09 21:28       ` Bob Rossi [this message]
2003-04-09 22:09         ` Elena Zannoni
2003-04-09 20:54 ` Elena Zannoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030409212815.GC22063@white \
    --to=bob_rossi@cox.net \
    --cc=ac131313@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox