public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: gdb@sourceware.org
Cc: Simon Sobisch <simonsobisch@gnu.org>
Subject: Re: How to create new mi commands via python / get current interpreter in python
Date: Tue, 02 Nov 2021 16:56:39 +0000	[thread overview]
Message-ID: <60c53fa8bf160533a2eddf1da280eb50c7461a6a.camel@fit.cvut.cz> (raw)
In-Reply-To: <e5e0522f-2847-1575-6dbd-3795fa6ebdb3@gnu.org>

Hi,

On Tue, 2021-11-02 at 17:40 +0100, Simon Sobisch via Gdb wrote:
> Additional to this question: is there an option to create new MI 
> commands from python (instead of "console commands")

Sort of. This has been started by Didier Nadeau and then continued by
me but sadly, I got carried away and have not done the last bits so it
can be pushed. 

However, I'm using this feature heavily and keep more-or-less 
up-to-date GDB with this support (and some other hacks/fixes waiting
to be polished and submitted, see

https://github.com/janvrany/binutils-gdb/tree/users/jv%2Fvdb

Here you may find example how I use it:

https://swing.fit.cvut.cz/hg/jv-vdb/file/tip/python/vdb/__init__.py#l329

Let me know if you have any questions, let me know.

I'd like to take the opportunity and apologise to all reviewers
for not finishing it yet - hopefuly I'll find long-enough period of
quiter time to finish this.

Jan


  reply	other threads:[~2021-11-02 16:56 UTC|newest]

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

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=60c53fa8bf160533a2eddf1da280eb50c7461a6a.camel@fit.cvut.cz \
    --to=jan.vrany@fit.cvut.cz \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).