public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ratmice at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11688] wrap MI commands in python
Date: Fri, 26 Aug 2011 07:08:00 -0000	[thread overview]
Message-ID: <bug-11688-4717-LkW8P7FjPq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11688-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11688

--- Comment #1 from matt rice <ratmice at gmail dot com> 2011-08-26 06:56:16 UTC ---
Created attachment 5914
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5914
a quick and ugly hack on this...

here is a quick ugly patch for this which i am abandoning, though
I got it partially working, the mi_execute() python function does
some truly awful things, such that I think that specific approach is a dead
end..

the py-mi-out needs error checking/a careful review of reference counting.
and it was only tested with -break-insert/-break-list and -trace-status.

I just think its more worth my time to do real python API's which have nicer
output, than the amount of effort that this will require to get this
functioning correctly and into a commitable form.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2011-08-26  6:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11688-4717@http.sourceware.org/bugzilla/>
2011-08-26  7:08 ` ratmice at gmail dot com [this message]
2011-08-26 12:31 ` ratmice at gmail dot com
2011-08-28 10:34 ` tromey at redhat dot com
2011-08-29 21:06 ` ratmice at gmail dot com
2012-01-02 19:44 ` tromey at redhat dot com
2012-01-03 21:59 ` ratmice at gmail dot com
2012-01-06 22:14 ` ratmice at gmail dot com
2012-01-06 22:17 ` ratmice at gmail dot com
2012-01-06 22:18 ` ratmice at gmail dot com
2023-03-23 18:04 ` tromey at sourceware dot org
2023-03-24 12:11 ` ratmice at gmail dot com
2023-03-24 16:18 ` tromey at sourceware dot org
2023-04-04 17:10 ` tromey at sourceware dot org
2023-05-23 19:48 ` cvs-commit at gcc dot gnu.org
2023-05-24 17:00 ` tromey at sourceware dot org

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=bug-11688-4717-LkW8P7FjPq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).