Coccinelle archive on
 help / color / Atom feed
From: Markus Elfring <>
To: Coccinelle <>
Subject: [Cocci] Navigation for source code positions from error messages
Date: Sun, 21 Apr 2019 18:33:43 +0200
Message-ID: <> (raw)


I try to achieve something also by the specification of Python code within
scripts for the semantic patch language.
It can happen then that such code contains questionable places
(because of usual update candidates).

Example for a corresponding error message:
  File "<string>", line 11
SyntaxError: can't assign to function call
Error in Python script, line 42, file …

I have got difficulties to follow the provided line numbers.
Can they belong to a SmPL rule “initialize” or “finalize”?
I hoped that the error situation would become clearer if I add rule names there.
But I wonder then again about information like the following.

rule name: parse error:
  whole content = @initialize:python start@

Can this software area be improved?

Cocci mailing list

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Coccinelle archive on

Archives are clonable:
	git clone --mirror cocci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 cocci cocci/ \
	public-inbox-index cocci

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox