|
Re: Enable tracing for CDT plug-in [message #146596 is a reply to message #146581] |
Tue, 07 June 2005 16:42 |
Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
You should use the full path. Also, the "-debug" argument should be added
before VM-related arguments.
"Jerome Correnoz" <jerome.correnoz@st.com> wrote in message
news:298d4750b13921df28f50a6f15fe1c2a$1@www.eclipse.org...
> Hi,
>
> I would like how to enable tracing for CDT plug-in ?
> In particular, I would like to trace MI commands sent by CDT to the gdb
> debugger.
>
> Note that I made some trials.
> I've tried to create a ".options" file that contains:
> org.eclipse.cdt.debug.mi.core/debug=true
>
> then launch eclipse with following arguments:
> -debug "file:.options"
> but it doesn't work.
> Can someone help me ?
>
> Thanks
> Jerome
>
>
|
|
|
|
Re: Enable tracing for CDT plug-in [message #146679 is a reply to message #146672] |
Thu, 09 June 2005 12:04 |
Eclipse User |
|
|
|
Originally posted by: mikhailkhod.rogers.com
Check if the file's path and name are correct. This line appears in the
console window regardless if the file exists or not. The common error on
Windows is that the file has an hidden extension, .txt for example.
We have been using this option since CDT 1.1 and it works fine.
"Jerome Correnoz" <jerome.correnoz@st.com> wrote in message
news:30c285c3901c6b366e097671d0b82b72$1@www.eclipse.org...
> Even if I use the full path and no VM arguments but it doesn't work...
>
> Nevertheless, I have a cmd window that opens with trace such as:
> "Debug options:
> file:/D:/Eclipse-3.0.1-SDK/.options loaded"
> So my ".options" file is loaded correctly but no MI traces.
>
> Note that I use CDT 2.1.1.
>
> Jerome
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02743 seconds