Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Sobisch via Gdb <gdb@sourceware.org>
To: gdb-patches@sourceware.org
Cc: gdb@sourceware.org
Subject: feature branch for creating MI commands with python (was: How to create new mi commands via python / get current interpreter in python)
Date: Fri, 5 Nov 2021 22:18:49 +0100	[thread overview]
Message-ID: <8001469a-1bed-febb-3dbc-3c72c4293033@gnu.org> (raw)
In-Reply-To: <4a86abc464db6ce661a0ae6d443da3b0b4bd52b2.camel@fit.cvut.cz>


Am 05.11.2021 um 19:51 schrieb Jan Vrany:
>>
>>> In any case that looks quite promising, would be nice to see it at
>>> least
>>> in a feature-branch in the official gdb repo until it is ready to
>>> be
>>> merged.
>>
>> Good idea, I can do that. I'll post here when done.
>>
>>
> 
> Done. Rebased on a recent master and pushed into branch:
> "users/jv/patches/feature-python-mi":
> 
> https://sourceware.org/git/?p=binutils-gdb.git;a=shortlog;h=refs/heads/users/jv/patches/feature-python-mi
> 
> HTH, Jan

Thanks, I think this discussion should now move to gdb-patches.
I'd be interested what is missing to integrate this for GDB 12 
(obviously a "stable" ABI would be needed).

I'm looking forward to read about that in gdb-patches (hopefully sooner 
than later).

Thanks again for taking the time to answer and for your work on 
improving GDB's Python API.

Simon

  reply	other threads:[~2021-11-05 21:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 16:40 How to create new mi commands via python / get current interpreter in python Simon Sobisch via Gdb
2021-11-02 16:56 ` Jan Vrany
2021-11-02 19:11   ` Simon Sobisch via Gdb
2021-11-03  9:06     ` Jan Vrany
2021-11-05 18:51       ` Jan Vrany
2021-11-05 21:18         ` Simon Sobisch via Gdb [this message]
2021-11-23 12:29           ` feature branch for creating MI commands with python (was: How to create new mi commands via python / get current interpreter in python) Jan Vrany
2021-11-23 12:48             ` Lancelot SIX via Gdb
2021-11-23 16:28               ` Jan Vrany
2021-11-03 16:31   ` How to get the full source location of a frame via python Simon Sobisch via Gdb
2021-11-03 20:07     ` Jan Vrany
2021-11-03 20:35       ` Simon Sobisch via Gdb
2021-11-03 20:50   ` UnicodeDecodeError on gdb.execute Simon Sobisch via Gdb
2021-11-03 21:55   ` Is "forward-search" also possible case insensitive? Simon Sobisch via Gdb
2021-11-05  9:14   ` Is there a way to know about current "until"/"advance" execution? Simon Sobisch via Gdb
2021-11-22 14:54   ` Is there a way to get a function's end address other than `disassemble`? Simon Sobisch via Gdb
2021-11-22 15:14     ` Andreas Schwab
2021-11-22 15:17       ` Simon Sobisch via Gdb
2021-11-25 19:28   ` Broken source view with Pygments and non-UTF-8 encoded source Simon Sobisch via Gdb
2021-11-26 11:16     ` Andrew Burgess via Gdb
2021-11-26 13:39       ` Andrew Burgess via Gdb

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=8001469a-1bed-febb-3dbc-3c72c4293033@gnu.org \
    --to=gdb@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simonsobisch@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