Debugger sometimes stalls when using "Step Into".

[and4cb]

If this is an inappropriate question, please let me know, but can one of the Administrators let me know what the likelihood is that this "step into" problem with the debugger will be solved in the next nightly release?  Should I be redirecting my question to the gdb forum?

Thanks for all of your hard work.

[oBFusCATed]

If this is an inappropriate question, please let me know, but can one of the Administrators let me know what the likelihood is that this "step into" problem with the debugger will be solved in the next nightly release? 

This is unlikely.

Should I be redirecting my question to the gdb forum?

No, the gdb/cli output is never meant to be parsed by a program, only humans.

[and4cb]

Should I be redirecting my question to the gdb forum?

No, the gdb/cli output is never meant to be parsed by a program, only humans.

I may not have stated my question correctly... Should I ask the people who make the gdb program to look into the "step into" error, or is this problem solely due to the fact that I am using C::B to implement the gdb program?

[oBFusCATed]

First C::B doesn't implement gdb, just uses it and tries to parse its output.
I doubt gdb people will care for this error, you can ask them, but most probably they won't help you.

[and4cb]

Thank you so much for taking the time to answer my questions.  I can see that you have many people to respond to, and I am grateful for your efforts.