Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Problem with "Automatically refresh registers" option
Problem with "Automatically refresh registers" option [message #138426] Fri, 11 February 2005 12:20 Go to next message
Jerome Correnoz is currently offline Jerome CorrenozFriend
Messages: 80
Registered: July 2009
Member
Hello,

The default settings in "Windows>preferences>C/C++>GDB MI", are:
debugger timeout=10000
launch timeout = 30000
Automatically refresh register=true
Automatically refresh shared libraries=true.

My problem is the following:
When I create a new Managed C Project, then add source files then Build my
project, in "Windows>preferences>C/C++>GDB MI", the General settings for
GDB MI are not consistent:
debugger timeout=0
launch timeout = 0
Automatically refresh register=false
Automatically refresh shared libraries=false

Does someone have any idea of this problem ? Is it a known bug ?

After exiting Eclipse then launch Eclipse again, the GDB MI settings are
OK:
debugger timeout=10000
launch timeout = 30000
Automatically refresh register=true
Automatically refresh shared libraries=true.


Thanks for advance
Jerome
Re: Problem with "Automatically refresh registers" option [message #138550 is a reply to message #138426] Fri, 11 February 2005 19:35 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mikhailk.qnx.com

I followed the steps you mentioned but I couldn't reproduce the problem.
Does it happen everytime when you create a new managed project?

"jerome correnoz" <jerome.correnoz@st.com> wrote in message
news:cui7vb$uu2$1@www.eclipse.org...
> Hello,
>
> The default settings in "Windows>preferences>C/C++>GDB MI", are: debugger
> timeout=10000
> launch timeout = 30000
> Automatically refresh register=true
> Automatically refresh shared libraries=true.
> My problem is the following:
> When I create a new Managed C Project, then add source files then Build my
> project, in "Windows>preferences>C/C++>GDB MI", the General settings for
> GDB MI are not consistent: debugger timeout=0
> launch timeout = 0
> Automatically refresh register=false
> Automatically refresh shared libraries=false
>
> Does someone have any idea of this problem ? Is it a known bug ?
>
> After exiting Eclipse then launch Eclipse again, the GDB MI settings are
> OK:
> debugger timeout=10000
> launch timeout = 30000
> Automatically refresh register=true
> Automatically refresh shared libraries=true.
>
> Thanks for advance
> Jerome
>
>
Re: Problem with "Automatically refresh registers" option [message #138753 is a reply to message #138550] Mon, 14 February 2005 12:46 Go to previous messageGo to next message
Jerome Correnoz is currently offline Jerome CorrenozFriend
Messages: 80
Registered: July 2009
Member
My problem was solved by adding the following lines in my plugin.xml

<extension
point="org.eclipse.core.runtime.preferences">
<initializer
class="org.eclipse.cdt.debug.mi.core.MIPreferenceInitializer "/>
</extension>

Otherwise, it happen everytime I create a new Managed Project from ST type.

Mikhail Khodjaiants wrote:

> I followed the steps you mentioned but I couldn't reproduce the problem.
> Does it happen everytime when you create a new managed project?

> "jerome correnoz" <jerome.correnoz@st.com> wrote in message
> news:cui7vb$uu2$1@www.eclipse.org...
>> Hello,
>>
>> The default settings in "Windows>preferences>C/C++>GDB MI", are: debugger
>> timeout=10000
>> launch timeout = 30000
>> Automatically refresh register=true
>> Automatically refresh shared libraries=true.
>> My problem is the following:
>> When I create a new Managed C Project, then add source files then Build my
>> project, in "Windows>preferences>C/C++>GDB MI", the General settings for
>> GDB MI are not consistent: debugger timeout=0
>> launch timeout = 0
>> Automatically refresh register=false
>> Automatically refresh shared libraries=false
>>
>> Does someone have any idea of this problem ? Is it a known bug ?
>>
>> After exiting Eclipse then launch Eclipse again, the GDB MI settings are
>> OK:
>> debugger timeout=10000
>> launch timeout = 30000
>> Automatically refresh register=true
>> Automatically refresh shared libraries=true.
>>
>> Thanks for advance
>> Jerome
>>
>>
Re: Problem with "Automatically refresh registers" option [message #138804 is a reply to message #138753] Mon, 14 February 2005 16:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mikhailkhod.rogers.com

What do you mean by "my plugin.xml"? These lines are in the plugin.xml file
of the "org.eclipse.cdt.debug.mi.core" plugin.

"jerome correnoz" <jerome.correnoz@st.com> wrote in message
news:cuq6k0$nkj$1@www.eclipse.org...
> My problem was solved by adding the following lines in my plugin.xml
>
> <extension
> point="org.eclipse.core.runtime.preferences">
> <initializer
> class="org.eclipse.cdt.debug.mi.core.MIPreferenceInitializer "/>
> </extension>
>
> Otherwise, it happen everytime I create a new Managed Project from ST
type.
>
> Mikhail Khodjaiants wrote:
>
> > I followed the steps you mentioned but I couldn't reproduce the problem.
> > Does it happen everytime when you create a new managed project?
>
> > "jerome correnoz" <jerome.correnoz@st.com> wrote in message
> > news:cui7vb$uu2$1@www.eclipse.org...
> >> Hello,
> >>
> >> The default settings in "Windows>preferences>C/C++>GDB MI", are:
debugger
> >> timeout=10000
> >> launch timeout = 30000
> >> Automatically refresh register=true
> >> Automatically refresh shared libraries=true.
> >> My problem is the following:
> >> When I create a new Managed C Project, then add source files then Build
my
> >> project, in "Windows>preferences>C/C++>GDB MI", the General settings
for
> >> GDB MI are not consistent: debugger timeout=0
> >> launch timeout = 0
> >> Automatically refresh register=false
> >> Automatically refresh shared libraries=false
> >>
> >> Does someone have any idea of this problem ? Is it a known bug ?
> >>
> >> After exiting Eclipse then launch Eclipse again, the GDB MI settings
are
> >> OK:
> >> debugger timeout=10000
> >> launch timeout = 30000
> >> Automatically refresh register=true
> >> Automatically refresh shared libraries=true.
> >>
> >> Thanks for advance
> >> Jerome
> >>
> >>
>
>
Re: Problem with "Automatically refresh registers" option [message #138876 is a reply to message #138804] Tue, 15 February 2005 09:12 Go to previous message
Jerome Correnoz is currently offline Jerome CorrenozFriend
Messages: 80
Registered: July 2009
Member
I've copied these lines in the plugin.xml of my toolchain plugin (ST100
core).

Mikhail Khodjaiants wrote:

> What do you mean by "my plugin.xml"? These lines are in the plugin.xml file
> of the "org.eclipse.cdt.debug.mi.core" plugin.

> "jerome correnoz" <jerome.correnoz@st.com> wrote in message
> news:cuq6k0$nkj$1@www.eclipse.org...
>> My problem was solved by adding the following lines in my plugin.xml
>>
>> <extension
>> point="org.eclipse.core.runtime.preferences">
>> <initializer
>> class="org.eclipse.cdt.debug.mi.core.MIPreferenceInitializer "/>
>> </extension>
>>
>> Otherwise, it happen everytime I create a new Managed Project from ST
> type.
>>
>> Mikhail Khodjaiants wrote:
>>
>> > I followed the steps you mentioned but I couldn't reproduce the problem.
>> > Does it happen everytime when you create a new managed project?
>>
>> > "jerome correnoz" <jerome.correnoz@st.com> wrote in message
>> > news:cui7vb$uu2$1@www.eclipse.org...
>> >> Hello,
>> >>
>> >> The default settings in "Windows>preferences>C/C++>GDB MI", are:
> debugger
>> >> timeout=10000
>> >> launch timeout = 30000
>> >> Automatically refresh register=true
>> >> Automatically refresh shared libraries=true.
>> >> My problem is the following:
>> >> When I create a new Managed C Project, then add source files then Build
> my
>> >> project, in "Windows>preferences>C/C++>GDB MI", the General settings
> for
>> >> GDB MI are not consistent: debugger timeout=0
>> >> launch timeout = 0
>> >> Automatically refresh register=false
>> >> Automatically refresh shared libraries=false
>> >>
>> >> Does someone have any idea of this problem ? Is it a known bug ?
>> >>
>> >> After exiting Eclipse then launch Eclipse again, the GDB MI settings
> are
>> >> OK:
>> >> debugger timeout=10000
>> >> launch timeout = 30000
>> >> Automatically refresh register=true
>> >> Automatically refresh shared libraries=true.
>> >>
>> >> Thanks for advance
>> >> Jerome
>> >>
>> >>
>>
>>
Previous Topic:C/C++ Indexer Problem: Include path not found (\usr\include) on windows XP with Cygwin
Next Topic:C/C++ Indexer Problem: Invalid arithmetic conversion in file.
Goto Forum:
  


Current Time: Sat Oct 19 15:06:17 GMT 2024

Powered by FUDForum. Page generated in 0.03918 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top