[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [cdt-debug-dev] Re: Quick Question: Tracing the launch (MikhailKhodjaiants)
|
Hey guys,
just my opinion on this:
- I would sure like to be able to see the full communication between eclipse and CDT
- It is OK that it is turned off by default at the moment since I agree that this is more for toolchain integrators than for actual C++ developers. But it would be a gread help in troubleshooting so it should be present even in release versions.
- I would sure prefer to be able to turn this on and off again anytime during a debug session compared to being able to turn it on or off at the start of the session for the whole session.
Thanks,
Norbert Ploett
-----Ursprüngliche Nachricht-----
Von: cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mikhail Khodjaiants
Gesendet: Mittwoch, 18. Januar 2006 20:59
An: CDT Debug developers list
Betreff: Re: [cdt-debug-dev] Re: Quick Question: Tracing the launch (MikhailKhodjaiants)
>In plain view in the GUI? Sounds great!
>Perhaps a "GDB troubleshooter" tab in the launch menu?
Actually, I was thinking of the "verbose" mode of the gdb console. So, you
can switch it on and off anytime during the session. But your proposal
sounds good too.
>It would be nice if the log *clearly* states the actual command line
>invoked. (I haven't looked at these logs in a while, perhaps CDT already
>does this).
What do you mean by this? Can you give an example?
----- Original Message -----
From: "Øyvind Harboe" <oyvind.harboe@xxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Wednesday, January 18, 2006 2:44 PM
Subject: [cdt-debug-dev] Re: Quick Question: Tracing the launch (Mikhail
Khodjaiants)
> I would suggest to add a launch option for verbose console output.
What do
> you think?
In plain view in the GUI? Sounds great!
Perhaps a "GDB troubleshooter" tab in the launch menu?
Another common pitfall I see is that GDB console commands work fine as
long as the MI interpreter is not used.
It would be nice if the log *clearly* states the actual command line
invoked. (I haven't looked at these logs in a while, perhaps CDT already
does this).
--
Øyvind Harboe
http://www.zylin.com
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
