[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 00/13] script language API for GDB
From: |
Doug Evans |
Subject: |
[PATCH 00/13] script language API for GDB |
Date: |
Thu, 05 Dec 2013 09:05:33 -0800 |
Hi.
My patch set to add a scripting API to GDB is ready for submission.
It sets things up so that adding Guile scripting is straightforward.
I've cc'd guile-users to apprise them of my progress.
I'll spare them the actual set of patches here,
though I plan to cc them when submitting the Guile port,
their input will be helpful.
The actual Guile port is ready ... just have some more docs to write. :-)
This patch set also has a nice effect of formalizing the interface from
GDB to Python (one aspect of which is that it removes the need for
a lot if #ifdef HAVE_PYTHON's, and it removes all the little stubs that
had to be provided when GDB was compiled --without-python).
The main patches are 02 and 03.
02 adds scripting.c, scripting.h, and scripting-priv.h.
03 updates python.c, python.h, and python-internal.h.
The rest are pretty-straightforward.
A lot of the change is mechanical:
- I want to have each ops "method" named ${lang}_${method_name}.
- Plus I want to have each API entry point have something in its
name that says "I am a scripting API entry point".
My first attempt used slang_ but that was thought to have
to much potential confusion with the slang scripting language.
Instead I've taken a minimalist approach and added "script"
to the function name.
E.g., apply_val_pretty_printer -> apply_val_script_pretty_printer
- Then I needed to move the interface enums defined in python.h
out and make the values have non-python-specific names.
I'm going to wait until after 7.7 has been branched
before checking anything in of course.
- [PATCH 00/13] script language API for GDB,
Doug Evans <=