again: ping: testcase for "absolute source" patch

Baurzhan Ismagulov
2005-05-05T11:01:11Z

Hello,

the recent discussion reminded me about the testcase I submitted in
http://sources.redhat.com/ml/gdb-patches/2004-08/msg00539.html . While
unrelated, it did help me understand the issue. There are relatively few
basic cases (like absolute / relative, compilation cwd present / absent,
etc., search path specified / not specified, etc.), it's their
permutations that kill. While the testcase doesn't cover them all, I
think it's a good start, especially if we are going to touch some
functionality affecting openp. The functionality is very basic and
breaks everything if anything goes wrong; it happened several times in
the past, thus the motivation for this testcase.

A short history: Michael Chastain was guiding me w.r.t. this testcase.
Basically, he had three issues with it:

1. The testcase didn't support build != host.

The overall consensus was that there were useful testcases that
didn't support build != host at the moment. Michael decided to
include them if they explicitly returned unresolved on remote hosts.
I added the check.

2. Michael wanted to understand it.

We had come relatively far, but Michael got a new job and apparently
didn't have much time to review the testcase since
http://sources.redhat.com/ml/gdb-patches/2004-10/msg00281.html .

3. There were four cases where I was not sure what we wanted to do, so I
marked them "fail".

I asked for feedback several times, but haven't received any answer.

So, I suggest that we review, polish and include this testcase. After
that, we can test it on more platforms and add new permutations for
non-POSIX names.

Comments?

With kind regards,
Baurzhan.