Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Debugging resource manager: (7 Items)
   
Debugging resource manager  
Hi,

I am developing a resource manager. Inside this resource manager, I have a pulse handling function to handle different 
pulse messages. I found that whenever a pulse happened, the IDE would automatically stop at the first line of my pulse 
handling and I had to press ‘continue’ button to resume my program. It is quite inconvenient for me.

Do you know how can I disable this feature so that my program stops only at where I set break points?


Thanks,
Re: Debugging resource manager  
Why does it stop? It should tell you at the top of the stack trace.

On 11-03-21 10:10 AM, "Gang Li" <community-noreply@qnx.com> wrote:

> Hi,
> 
> I am developing a resource manager. Inside this resource manager, I have a
> pulse handling function to handle different pulse messages. I found that
> whenever a pulse happened, the IDE would automatically stop at the first line
> of my pulse handling and I had to press Œcontinue¹ button to resume my
> program. It is quite inconvenient for me.
> 
> Do you know how can I disable this feature so that my program stops only at
> where I set break points?
> 
> 
> Thanks,
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post84131
> 

RE: Debugging resource manager  
Either it crashed, it's a signal handler or you have a breakpoint set at that line.

> -----Message d'origine-----
> De : Gang Li [mailto:community-noreply@qnx.com]
> Envoyé : 21 mars 2011 13:10
> À : general-ide
> Objet : Debugging resource manager
> 
> Hi,
> 
> I am developing a resource manager. Inside this resource manager, I have a
> pulse handling function to handle different pulse messages. I found that
> whenever a pulse happened, the IDE would automatically stop at the first
> line of my pulse handling and I had to press ‘continue’ button to resume my
> program. It is quite inconvenient for me.
> 
> Do you know how can I disable this feature so that my program stops only at
> where I set break points?
> 
> 
> Thanks,
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post84131
Re: RE: Debugging resource manager  
This is a pulse message handler attached to a dispatch message channel within  my resource manager.

When debugger stops at the first line of my pulse handler function, it says breakpoint hit. However I did not set any 
breakpoint in my pulse handler function.

I think there must be options to override this default behavior.

Thanks,
RE: RE: Debugging resource manager  
If it says breakpoint hit then it hit a breakpoint.  This is  NOT a default behaviour. If you look in the breakpoint 
view,  do you see any breakpoint?

> -----Message d'origine-----
> De : Gang Li [mailto:community-noreply@qnx.com]
> Envoyé : 21 mars 2011 16:47
> À : general-ide
> Objet : Re: RE: Debugging resource manager
> 
> This is a pulse message handler attached to a dispatch message channel
> within  my resource manager.
> 
> When debugger stops at the first line of my pulse handler function, it says
> breakpoint hit. However I did not set any breakpoint in my pulse handler
> function.
> 
> I think there must be options to override this default behavior.
> 
> Thanks,
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post84147
> 
Re: RE: RE: Debugging resource manager  
This problem was caused by an invalid breakpoint. When the program is being debugged, the invalid breakpoint was 
automatically moved to the next valid line of code. However, the breakpoint marker in Momentics IDE was not changed, 
making this problem hard to be found.
Re: RE: RE: Debugging resource manager  
To be clear: it is gdb's feature to move the breakpoint to the next
line :-).

If IDE was moving the breakpoint marker that would introduce other kinds
of confusions like "why did my breakpoint move???"

On Tue, 2011-03-22 at 10:44 -0400, Gang Li wrote:
> This problem was caused by an invalid breakpoint. When the program is
> being debugged, the invalid breakpoint was automatically moved to the
> next valid line of code. However, the breakpoint marker in Momentics
> IDE was not changed, making this problem hard to be found.
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post84170
> 
> 
>