This is the mail archive of the
mailing list for the GDB project.
Re: RFC: MI output during program execution
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Stan Shebs <shebs at apple dot com>
- Cc: Jim Ingham <jingham at apple dot com>,Daniel Jacobowitz <drow at false dot org>, gdb-patches at sources dot redhat dot com
- Date: Mon, 12 Sep 2005 14:51:47 +1200
- Subject: Re: RFC: MI output during program execution
- References: <firstname.lastname@example.org><20050808130516.GA9046@nevyn.them.org><FDDE6A38-89E2-455B-BD32-08B6B75006D5@apple.com><email@example.com><430B9BF8.firstname.lastname@example.org>
Stan Shebs writes:
> >Could you please tell me where you think the best place to start would be?
> >I guess CVS would be better than a tarball. Would it be best to wait until
> >Stan & Klee have completed their merge?
> Anything you do now will be of value, I don't think our MI stuff
> has churned a whole lot, but I would like to put out a drop of
> our latest mostly-working CVS anyway, since it's merged up to FSF
> sources as of a few days ago, plus most of the local changes have
> been at least categorized by purpose. I can't think of any obstacles,
> but as a "newbie" in Apple GDB :-) , I need to find out what I can do.
I've started a merge on current CVS (for some reason gdb-413 seemed to include
everything except the GDB source). Getting MI output during program execution
seems to be closely related to making GDB asynchronous. I couldn't attempt
such a task on my own but, using the Apple code as a prototype, it doesn't
look too difficult. When I have something working perhaps I could put it on a
branch. It's not something that I'll complete in the next week or so and I
just wanted to outline my intentions. It will probably only work on the
platform that I've got (GNU/Linux) so maybe someone more knowledgeable than
myself can beef it up to make it general enough for mainline.