From: Elena Zannoni <ezannoni@redhat.com>
To: edmund vorauer <edi@takefive.co.at>
Cc: gdb@sources.redhat.com
Subject: Re: gdb/mi: may i help ?
Date: Wed, 09 Jan 2002 07:14:00 -0000 [thread overview]
Message-ID: <15420.21315.594875.625814@localhost.cygnus.com> (raw)
In-Reply-To: <3C3C5545.DCB166A3@takefive.co.at>
edmund vorauer writes:
> hi,
>
> some of the documented gdb/mi commands
> are not implemented;
Yes, correct.
> is anyone actively working on them ?
Apple is using the MI interface for their gdb, so I think they are
probably working on it. There is a source drop of Apple's tree in
ftp://sources.redhat.com/pub/gdb/contrib/apple/
> if not, i'd like to take over this task;
>
That would be great, thanks.
> please give me advice ...
Make sure you have an assignment in place with the FSF. Have a look at
http://sources.redhat.com/gdb/contribute/
for more information.
>
> edi
Elena
next prev parent reply other threads:[~2002-01-09 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 6:24 edmund vorauer
2002-01-09 7:14 ` Elena Zannoni [this message]
2002-01-10 9:22 ` edmund vorauer
2002-01-10 10:19 ` Andrew Cagney
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=15420.21315.594875.625814@localhost.cygnus.com \
--to=ezannoni@redhat.com \
--cc=edi@takefive.co.at \
--cc=gdb@sources.redhat.com \
/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