From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/9] Code cleanup: Drop IS_ABSOLUTE_PATH checks
Date: Sat, 19 Jan 2013 15:27:00 -0000 [thread overview]
Message-ID: <20130119152731.GA10298@host2.jankratochvil.net> (raw)
In-Reply-To: <834nidqjz2.fsf@gnu.org>
On Sat, 19 Jan 2013 16:18:57 +0100, Eli Zaretskii wrote:
> > For example when asking for a breakpoint at:
> > c:\filename.c:main
> > it must not match a debug info filename:
> > d:\foo\c:\filename.c
>
> Why not?
Not sure how to reply that.
One uses absolute filenames (SEARCH_NAME in this case) to prevent any
ambiguities (resolved as multi-location breakpoints by GDB) due to the
dependence on "current directory" (which does not exist in GDB during linespec
resolution).
If an absolute filename can match trailing part of a longer filename then it
is not absolute filename by definition.
"c:\filename.c" is absolute filename by definition so it must not match
trailing part of a longer filename.
> Whatever. I'm still unconvinced, I think the code is not sufficiently
> cleaned up. But I'm tired of arguing.
Me too. I will try to add some comment there in a next patch.
Thanks,
Jan
next prev parent reply other threads:[~2013-01-19 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 21:59 Jan Kratochvil
2013-01-18 7:32 ` Eli Zaretskii
2013-01-18 18:39 ` Jan Kratochvil
2013-01-18 19:20 ` Eli Zaretskii
2013-01-18 20:16 ` Jan Kratochvil
2013-01-18 20:40 ` Eli Zaretskii
2013-01-18 21:53 ` Jan Kratochvil
2013-01-19 6:50 ` Eli Zaretskii
2013-01-19 14:09 ` Jan Kratochvil
2013-01-19 15:18 ` Eli Zaretskii
2013-01-19 15:27 ` Jan Kratochvil [this message]
2013-01-19 16:02 ` Eli Zaretskii
2013-01-21 17:06 ` Jan Kratochvil
2013-01-21 18:46 ` Tom Tromey
2013-01-21 19:43 ` Jan Kratochvil
2013-01-21 20:48 ` Tom Tromey
2013-01-18 21:11 ` [patch 2/9] Code cleanup: Drop IS_ABSOLUTE_PATH checks [resent] Jan Kratochvil
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=20130119152731.GA10298@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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