Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: kettenis@chello.nl
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] lib/gdb.exp: native tcl gdb_get_line_number
Date: Mon, 09 Aug 2004 19:47:00 -0000	[thread overview]
Message-ID: <4117D4E9.nailNML1MZER2@mindspring.com> (raw)
In-Reply-To: <200408091755.i79Hta9D038666@elgar.kettenis.dyndns.org>

Mark Kettenis <kettenis@chello.nl> wrote:
> This causes problems if you configure using a relative pathname, i.e.
>
>   ../src/configure --enable-gdb-build-warnings=,-Werror

Oof.  I forgot all about relative pathnames.

> The attached patch fixes things for me, but can somebody please check
> whether i've escaped the dot correctly?

I'm going to think about this problem a bit.  I don't really like that
compatibility kludge in the first place, and I'd rather bust some heads
in the callers and de-kludge this rather then en-kludge it some more.
So this patch is not approved.  (If I don't get the problem fixed pretty
quick then I'll have to accept it though).

Which files are causing problems on your system?  On my system,
the intersection between gdb_get_line_number and ${srcfile*} with
a "/" in them is:

  gdb.cp/ctti.exp
  gdb.cp/m-static.exp

So I would have to change two callers.

In the long run I want to go further and change all the callers to
explicitly specify a filename and then kill off the kludge.
But that's not suitable for right now.

Michael C


  reply	other threads:[~2004-08-09 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08 16:14 Michael Chastain
2004-08-09 17:55 ` Mark Kettenis
2004-08-09 19:47   ` Michael Chastain [this message]
2004-08-09 20:22     ` Mark Kettenis
2004-08-09 22:18       ` [rfc/testsuite/cp] make all srcfile look the same Michael Chastain
2004-08-15  9:21         ` Michael Chastain

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=4117D4E9.nailNML1MZER2@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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