From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32730 invoked by alias); 5 May 2005 11:01:11 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32428 invoked from network); 5 May 2005 11:00:58 -0000 Received: from unknown (HELO mail-in-08.arcor-online.net) (151.189.21.48) by sourceware.org with SMTP; 5 May 2005 11:00:58 -0000 Received: from mail-in-08-z2.arcor-online.net (mail-in-08-z2.arcor-online.net [151.189.8.20]) by mail-in-08.arcor-online.net (Postfix) with ESMTP id 197641341D for ; Thu, 5 May 2005 13:00:58 +0200 (CEST) Received: from mail-in-03.arcor-online.net (mail-in-06.arcor-online.net [151.189.21.46]) by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id 019CD72466 for ; Thu, 5 May 2005 13:00:58 +0200 (CEST) Received: from alatau.radix50.net (dsl-082-083-192-231.arcor-ip.net [82.83.192.231]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 1730BFE88 for ; Thu, 5 May 2005 13:00:56 +0200 (CEST) Received: from alatau.radix50.net (localhost [127.0.0.1]) by alatau.radix50.net (8.13.4/8.13.4/Debian-1) with ESMTP id j45B0rmX007412 for ; Thu, 5 May 2005 13:00:53 +0200 Received: (from ibr@localhost) by alatau.radix50.net (8.13.4/8.13.4/Submit) id j45B0mh4007411 for gdb-patches@sources.redhat.com; Thu, 5 May 2005 13:00:48 +0200 Date: Thu, 05 May 2005 11:01:00 -0000 From: Baurzhan Ismagulov To: gdb-patches@sources.redhat.com Subject: again: ping: testcase for "absolute source" patch Message-ID: <20050505110048.GC5840@radix50.net> Mail-Followup-To: gdb-patches@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-05/txt/msg00158.txt.bz2 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.