[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Observing MI traffic
|
Simon is right.
And here as some pics to help:
https://wiki.eclipse.org/CDT/User/FAQ#I.27ve_been_asked_for_.27gdb_traces.27.2C_where_can_I_find_them.3F
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Simon Marchi
> Sent: Monday, June 23, 2014 3:52 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Observing MI traffic
>
> On Mon 23 Jun 2014 03:37:40 PM EDT, Pascal Rapicault wrote:
> > Hi,
> >
> > Is there a tool of some sort, or maybe just a technique to observe the
> > traffic ongoing between the CDT debugger and gdb?
>
> Hi Pascal,
>
> You can see them directly in CDT, they are called "gdb traces". In the Console
> View, you can switch between the different consoles (it's a small arrow
> pointing down, just right of the computer screen icon).
> There is one console that should contain "gdb traces" in its name.
>
> Commands sent to gdb are prefixed with a number (just a running
> counter) and the corresponding reply is also prefixed with that number.
> This way, you (and CDT) can associate a request and its reply. Example:
>
> 900,946 19-list-thread-groups
> 900,947 19^done,groups=[{id="i1",type="process"}]
>
> Hope this helps,
>
> Simon
>
> > thx
> >
> > Pascal
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
