public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-tromey-python-checker: add README.archer
Date: Fri, 22 Feb 2013 19:04:00 -0000	[thread overview]
Message-ID: <20130222190403.32729.qmail@sourceware.org> (raw)

The branch, archer-tromey-python-checker has been updated
       via  b8b589ef1e9aeddb2600fce6cf13b8890e14a8eb (commit)
      from  cb8896605a919d2fe55816025515506047266434 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit b8b589ef1e9aeddb2600fce6cf13b8890e14a8eb
Author: Tom Tromey <tromey@redhat.com>
Date:   Fri Feb 22 12:03:50 2013 -0700

    add README.archer

-----------------------------------------------------------------------

Summary of changes:
 README.archer |   13 +++++++++++++
 1 files changed, 13 insertions(+), 0 deletions(-)
 create mode 100644 README.archer

First 500 lines of diff:
diff --git a/README.archer b/README.archer
new file mode 100644
index 0000000..f3c50db
--- /dev/null
+++ b/README.archer
@@ -0,0 +1,13 @@
+This branch holds some changes for use with the CPython checker:
+
+    https://gcc-python-plugin.readthedocs.org/en/latest/cpychecker.html
+
+Mostly this consists of adding attributes to various declarations, so
+that the checker can do its work.
+
+A few useful attributes have been added since this branch was written,
+for example, "cpychecker_sets_exception".
+
+The checker doesn't fully work on gdb due to cleanups.  We would have
+to teach it about these specially, or avoid their use in the Python
+layer.


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2013-02-22 19:04 UTC|newest]

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

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=20130222190403.32729.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).