Re: RFC: MI output during program execution

Nick Roberts
2005-09-19T22:12:55Z

[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 1148 bytes --]

Daniel Jacobowitz writes:
> The rules for a branch are, generally, up to the branch owner. The
> only one I'll insist on is that copyright assignments be handled in the
> same way as for HEAD, which is not a problem here.

You mean if someone else contributes a patch? My changes are covered by the
assignment that I have already made for GDB. Apple's changes are presumably
covered similarly.

> See:
>
> http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC133
> (which are mostly guidelines rather than rules). So, you can create a
> branch if you'd like.

OK. Thats helpful

> I took a quick look at the changes, but couldn't make heads or tails
> out of what was going on. Also, I think the diff is corrupted; the
> changes to linux-nat.c cut off in a very strange place in child_wait().

Yes. It seems to have also corrupted Makefile.in. Its an ssh problem. I've
resolved that and attach a new patch which should work hopefully.

> Maybe when it's been cleaned up a little we can look for a way to do
> this that doesn't involve pthreads.

Nick

[-- Attachment #2: Asynchronous GDB (2) --]
[-- Type: application/octet-stream, Size: 26260 bytes --]