From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 798B3C282C3 for ; Tue, 22 Jan 2019 19:53:33 +0000 (UTC) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 197DD20870 for ; Tue, 22 Jan 2019 19:53:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 197DD20870 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lip6.fr Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=cocci-bounces@systeme.lip6.fr Received: from systeme.lip6.fr (systeme.lip6.fr [132.227.104.7]) by isis.lip6.fr (8.15.2/lip6) with ESMTP id x0MJrKod023905 ; Tue, 22 Jan 2019 20:53:20 +0100 (CET) Received: from systeme.lip6.fr (systeme.lip6.fr [127.0.0.1]) by systeme.lip6.fr (Postfix) with ESMTP id 05D5776F2; Tue, 22 Jan 2019 20:53:20 +0100 (CET) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by systeme.lip6.fr (Postfix) with ESMTPS id DF6FA76EA for ; Tue, 22 Jan 2019 20:53:18 +0100 (CET) Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by isis.lip6.fr (8.15.2/lip6) with ESMTP id x0MJrIfg020769 for ; Tue, 22 Jan 2019 20:53:18 +0100 (CET) X-pt: isis.lip6.fr X-Addr-Warning: ATTENTION - Votre correspondant a fourni une adresse d'enveloppe @lip6.fr, mais ce message ne provient pas de lip6.fr ! postmaster@lip6.fr. X-IronPort-AV: E=Sophos;i="5.56,508,1539640800"; d="scan'208";a="365311232" Received: from abo-58-107-68.mrs.modulonet.fr (HELO hadrien) ([85.68.107.58]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2019 20:44:00 +0100 Date: Tue, 22 Jan 2019 20:44:00 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Timur Tabi In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, Sender e-mail whitelisted, not delayed by milter-greylist-4.4.3 (isis.lip6.fr [132.227.60.2]); Tue, 22 Jan 2019 20:53:20 +0100 (CET) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.4.3 (isis.lip6.fr [132.227.60.2]); Tue, 22 Jan 2019 20:53:18 +0100 (CET) X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2 X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2 Cc: cocci Subject: Re: [Cocci] Fatal exception in spatch when #include file does not exist X-BeenThere: cocci@systeme.lip6.fr X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: cocci-bounces@systeme.lip6.fr Errors-To: cocci-bounces@systeme.lip6.fr On Tue, 22 Jan 2019, Timur Tabi wrote: > Let's say I have these files: > > dir1/dir2/dir3/file1.h > dir1/dir2/dir4/dir5/file2.c > > In file2.c, I have this include statement: > > #include "../../dir3/file1.h" > > This works if I compile the file when I'm in the dir5 directory. > > However, if I am in the dir4 directory and do this: > > spatch ... ./dir5/file2.c > > I will get this error: > > Fatal error: exception Sys_error("../../dir3/file1.h": No such file or > directory") > > which is technically true, but so what? Does spatch actually try to > read the contents of file1.h? If not, why does it care whether the > file exists? And why doesn't it just ignore the #include line? If you get such a message, it means that the options were such that it wants to read the header file. By default, the option is --local-includes which includes things mentioned with " " and headers with the same name as the .c file. I guess that it is not interpreting the ../ properly, at least when you specify a path to a specific file. If you want all the header files to be ignored, just give the argument --no-includes. If you give the argument --include-headers and give spatch the name of a directory or of a .h file, it will process individually the .h files as well as the .c files julia _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci