[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] GDB/MI Issues
|
> Hi,
Bonjour
>
> I don't know who's on this list or if this list is still being used,
> but... I wanted to follow-up yesterday's meeting (graciously hosted by
> QNX -- thanks!): Is there a list of gdb and/or mi issues that you have?
This one should be fine.
>
> We came out of the meeting yesterday believing that the best thing we
> could do for this project right now is to work on gdb/mi. We have a list
> of TODOs based on my own experience with mi and another gdb UI, but I
> would like feedback from your developers to help guide us in our
> understanding of the issues and the prioritization that we give them.
Probably Mikhailk, will comment more on this later.
And also if you look at the mailing list archive, you will find
an interresting piece from Brian Thompson(IBM) on the pros and cons of MI.
Mikhail just put on the web an overall API for debug(It should be
consider as an interim API, subject to changes, when we get more feedbacks).
In the next days/weeks, we'll be looking at a ways to implement
this using gdb/mi(5.2), when we got some workable or at least "compilable"
set of classes, it will be put under CVS. Meanwhile, if you already
have some ideas on how to tackle this, please feel free to fire me some emails.
>
> Keith
>
> PS. If you have specific gdb/mi issues (bugs), please submit a bug to the
> public bug database (http://sources.redhat.com/gdb/bugs -- click on "bug
> database").
Ok, thanks for the pointers.
