Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Debugging doesn't work anymore
Debugging doesn't work anymore [message #234888] Wed, 17 June 2009 04:07 Go to next message
Eclipse UserFriend
Hi!

I'm using eclipse since some days and it works fine!
I have eclipse 3.4.1 CDT with GDB included.

It works fine to debug with gdb. But since yesterday it works not
anylonger...
Eclipse just doesn't stop at the breakpoints, I must have changed
something, but I have no clue what... The only thin I can say, that the
symbol for the breakpoint before was a blue dot with a little hook at
its lift side. Now I have just the blue dot without hook... Is it
possible that this indicates the impossibility to stop at this breakpoint?

Thanks for your help!
Re: Debugging doesn't work anymore [message #234895 is a reply to message #234888] Wed, 17 June 2009 05:09 Go to previous messageGo to next message
Eclipse UserFriend
Perhaps you activated "Skip all breakpoints". In the Debug View is a icon
with a blue ball that is crossed out. It should not be activated.
BTW, the blue dot with a hook marks a breakpoint with a condition. A blue
dot without anything is a normal breakpoint.

Axel

> Hi!

> I'm using eclipse since some days and it works fine!
> I have eclipse 3.4.1 CDT with GDB included.

> It works fine to debug with gdb. But since yesterday it works not
> anylonger...
> Eclipse just doesn't stop at the breakpoints, I must have changed
> something, but I have no clue what... The only thin I can say, that the
> symbol for the breakpoint before was a blue dot with a little hook at
> its lift side. Now I have just the blue dot without hook... Is it
> possible that this indicates the impossibility to stop at this breakpoint?

> Thanks for your help!
Re: Debugging doesn't work anymore [message #234898 is a reply to message #234895] Wed, 17 June 2009 05:45 Go to previous messageGo to next message
Eclipse UserFriend
Axel Mueller schrieb:
> Perhaps you activated "Skip all breakpoints". In the Debug View is a
> icon with a blue ball that is crossed out. It should not be activated.
> BTW, the blue dot with a hook marks a breakpoint with a condition. A
> blue dot without anything is a normal breakpoint.
>
> Axel
>
>> Hi!
>
>> I'm using eclipse since some days and it works fine!
>> I have eclipse 3.4.1 CDT with GDB included.
>
>> It works fine to debug with gdb. But since yesterday it works not
>> anylonger...
>> Eclipse just doesn't stop at the breakpoints, I must have changed
>> something, but I have no clue what... The only thin I can say, that
>> the symbol for the breakpoint before was a blue dot with a little hook
>> at its lift side. Now I have just the blue dot without hook... Is it
>> possible that this indicates the impossibility to stop at this
>> breakpoint?
>
>> Thanks for your help!
>
>

No, I didn't skip the breakpoint... Thanks for the info with the
condition. But the one with the hook has no condition in its properties
:-( Are you sure...

What I just saw is, that if I press "Show Breakpoints Supported by
Selected Target", one breakpoit disappears (the one without hook) and
the other one stays (the one with the hook). What does this "Breakpoint
Supported by Selected Target" exactly mean?
Re: Debugging doesn't work anymore [message #234903 is a reply to message #234898] Wed, 17 June 2009 07:53 Go to previous messageGo to next message
Eclipse UserFriend
Michael Schmid schrieb:
> Axel Mueller schrieb:
>> Perhaps you activated "Skip all breakpoints". In the Debug View is a
>> icon with a blue ball that is crossed out. It should not be activated.
>> BTW, the blue dot with a hook marks a breakpoint with a condition. A
>> blue dot without anything is a normal breakpoint.
>>
>> Axel
>>
>>> Hi!
>>
>>> I'm using eclipse since some days and it works fine!
>>> I have eclipse 3.4.1 CDT with GDB included.
>>
>>> It works fine to debug with gdb. But since yesterday it works not
>>> anylonger...
>>> Eclipse just doesn't stop at the breakpoints, I must have changed
>>> something, but I have no clue what... The only thin I can say, that
>>> the symbol for the breakpoint before was a blue dot with a little
>>> hook at its lift side. Now I have just the blue dot without hook...
>>> Is it possible that this indicates the impossibility to stop at this
>>> breakpoint?
>>
>>> Thanks for your help!
>>
>>
>
> No, I didn't skip the breakpoint... Thanks for the info with the
> condition. But the one with the hook has no condition in its properties
> :-( Are you sure...
>
> What I just saw is, that if I press "Show Breakpoints Supported by
> Selected Target", one breakpoit disappears (the one without hook) and
> the other one stays (the one with the hook). What does this "Breakpoint
> Supported by Selected Target" exactly mean?

It seems to me, that I can only set breakpoints in main.cxx but not in
the other files? Anyone an idea what this could be?
Re: Debugging doesn't work anymore [message #234914 is a reply to message #234903] Wed, 17 June 2009 10:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: wegener.cboenospam.com

"Michael Schmid" <schmid@ecom-ch.com> wrote in message
news:h1alg4$37g$1@build.eclipse.org...
> Michael Schmid schrieb:
> > Axel Mueller schrieb:
> >> Perhaps you activated "Skip all breakpoints". In the Debug View is a
> >> icon with a blue ball that is crossed out. It should not be activated.
> >> BTW, the blue dot with a hook marks a breakpoint with a condition. A
> >> blue dot without anything is a normal breakpoint.
> >>
> >> Axel
> >>
> >>> Hi!
> >>
> >>> I'm using eclipse since some days and it works fine!
> >>> I have eclipse 3.4.1 CDT with GDB included.
> >>
> >>> It works fine to debug with gdb. But since yesterday it works not
> >>> anylonger...
> >>> Eclipse just doesn't stop at the breakpoints, I must have changed
> >>> something, but I have no clue what... The only thin I can say, that
> >>> the symbol for the breakpoint before was a blue dot with a little
> >>> hook at its lift side. Now I have just the blue dot without hook...
> >>> Is it possible that this indicates the impossibility to stop at this
> >>> breakpoint?
> >>
> >>> Thanks for your help!
> >>
> >>
> >
> > No, I didn't skip the breakpoint... Thanks for the info with the
> > condition. But the one with the hook has no condition in its properties
> > :-( Are you sure...
> >
> > What I just saw is, that if I press "Show Breakpoints Supported by
> > Selected Target", one breakpoit disappears (the one without hook) and
> > the other one stays (the one with the hook). What does this "Breakpoint
> > Supported by Selected Target" exactly mean?
>
> It seems to me, that I can only set breakpoints in main.cxx but not in
> the other files? Anyone an idea what this could be?

Make sure you are building with debugging enabled. Debugging symbols need
to be included in order for breakpoints to be located. You need to have
debugging enabled for both compile and link.
Re: Debugging doesn't work anymore [message #234926 is a reply to message #234914] Thu, 18 June 2009 02:10 Go to previous message
Eclipse UserFriend
Dave Wegener schrieb:
> "Michael Schmid" <schmid@ecom-ch.com> wrote in message
> news:h1alg4$37g$1@build.eclipse.org...
>> Michael Schmid schrieb:
>>> Axel Mueller schrieb:
>>>> Perhaps you activated "Skip all breakpoints". In the Debug View is a
>>>> icon with a blue ball that is crossed out. It should not be activated.
>>>> BTW, the blue dot with a hook marks a breakpoint with a condition. A
>>>> blue dot without anything is a normal breakpoint.
>>>>
>>>> Axel
>>>>
>>>>> Hi!
>>>>> I'm using eclipse since some days and it works fine!
>>>>> I have eclipse 3.4.1 CDT with GDB included.
>>>>> It works fine to debug with gdb. But since yesterday it works not
>>>>> anylonger...
>>>>> Eclipse just doesn't stop at the breakpoints, I must have changed
>>>>> something, but I have no clue what... The only thin I can say, that
>>>>> the symbol for the breakpoint before was a blue dot with a little
>>>>> hook at its lift side. Now I have just the blue dot without hook...
>>>>> Is it possible that this indicates the impossibility to stop at this
>>>>> breakpoint?
>>>>> Thanks for your help!
>>>>
>>> No, I didn't skip the breakpoint... Thanks for the info with the
>>> condition. But the one with the hook has no condition in its properties
>>> :-( Are you sure...
>>>
>>> What I just saw is, that if I press "Show Breakpoints Supported by
>>> Selected Target", one breakpoit disappears (the one without hook) and
>>> the other one stays (the one with the hook). What does this "Breakpoint
>>> Supported by Selected Target" exactly mean?
>> It seems to me, that I can only set breakpoints in main.cxx but not in
>> the other files? Anyone an idea what this could be?
>
> Make sure you are building with debugging enabled. Debugging symbols need
> to be included in order for breakpoints to be located. You need to have
> debugging enabled for both compile and link.
>
>

Found the problem. I compile one time for my Desktop-PC and one time for
PPC (Target). Now I have for both Systems the same source-files, but in
the two eclipse-projects there are just links to this files. So if I
change one sourcefile both systems apply the change. BUT if I open a
sourcefile, for example listed under the Desktop-PC-Projekt, and set
there a breakpoint and debug the Target (PPC) then theres no breakpoint
for PPC :-) Which is logical, but I didn't think about that...
I hope you understood, my mothertongue is not enlish.... ;-)
Previous Topic:Non-Java Installer Plug-in
Next Topic:Programmatically populate Discovery options ("Load build output from file")
Goto Forum:
  


Current Time: Tue May 13 07:53:23 EDT 2025

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

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

Back to the top