public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org, guile-user@gnu.org
Subject: [PATCH v1 00/36] Guile extension language
Date: Tue, 24 Dec 2013 19:00:00 -0000	[thread overview]
Message-ID: <m34n5yt6ph.fsf@sspiff.org> (raw)

Hi.

This patch series is a first pass at adding support for the
Guile extension language.  A lot is working, but there's
still a ways to go.  And I still have more docs to write,
but what's there now is ready for review.

guile-user: I'm going to avoid spamming you with the entire series of
36 emails.  But I may add you back to the discussion of a particular patch.

This patch series requires v3 of the "extension language API"
patch series:
https://sourceware.org/ml/gdb-patches/2013-12/msg00906.html

Summary of each patch:

01/36: configure changes
02/36: doc additions
03/36: auto-load.c changes
04/36: breakpoint.c changes
05/36: cli changes
06/36: gdbtypes.c additions
07/36: extension.c additions
08/36: guile/README
09/36: gdb-guile.exp
10/36: guile.c, guile.h
11/36: scm-auto-load.c
12/36: scm-smob.c
13/36: scm-exception.c, scm-safe-call.c
14/36: scm-ports.c
15/36: scm-string.c
16/36: scm-utils.c
17/36: scm-iterator.c
18/36: scm-arch.c
19/36: scm-block.c
20/36: scm-breakpoint.c
21/36: scm-disasm.c
22/36: scm-frame.c
23/36: scm-lazy-string.c
24/36: scm-math.c
25/36: scm-objfile.c
26/36: scm-pretty-print.c
27/36: scm-symbol.c
28/36: scm-symtab.c
29/36: scm-type.c
30/36: scm-value.c
31/36: Scheme files
32/36: help.exp update
33/36: generic,goops tests
34/36: equal? tests
35/36: error tests
36/36: section script tests

                 reply	other threads:[~2013-12-24 19:00 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=m34n5yt6ph.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@gnu.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).