User forums > Help
Debugger sometimes stalls when using "Step Into".
MortenMacFly:
--- Quote from: and4cb on November 22, 2012, 10:06:37 am ---MortenMacFly: I have downloaded your patch, but please provide me with instructions on how to apply the patch. I have never applied a patch before. Thank you.
--- End quote ---
It requires you to self-compile C::B from the sources and modify the files using the "patch" tool. You'll find instructions in the WiKi accordingly for each platform. However, if you never did you maybe should not worry and let others try. Its not an easy task and requires knowledge about version control, third party libs dev packages, patching sources (using diff/patch) with specific platform tools and so on... There is plenty of help around in the WiKi, too and (of course) in the WWW on that topic.
and4cb:
--- Quote from: MortenMacFly on November 22, 2012, 10:17:25 am ---It requires you to self-compile C::B from the sources and modify the files using the "patch" tool.
...
However, if you never did you maybe should not worry and let others try.
--- End quote ---
MortenMacFly: I will take your advice at this time and let those that are more educated in this process handle the testing. I do not want my learning curve to hinder the problem being solved/tested. However, I am adding this to my list of "things to learn", as it does sound like a useful skill.
If this patch is successful, will it be included in the next "nightly" that is published?
Thank you so much for your quick replies.
oBFusCATed:
--- Quote from: MortenMacFly on November 22, 2012, 09:13:09 am ---What prompt do you mean? This one:
No stack.
? (Should be as easy as to add it to the entry I just made into trunk for the "Function out of bounds thing".
--- End quote ---
No, this one: ">>>>>>cb_gdb:"
If we detect this string as program stopped event, all other case could be removed, probably.
--- Quote from: MortenMacFly on November 22, 2012, 09:13:09 am ---Will you take the action?
--- End quote ---
I doubt, I have some other things to do and this change will require major effort and testing.
oBFusCATed:
Morten this commit is useless... r8596, because if you look at the initial log you'll see that the "No stack" string is not present there.
MortenMacFly:
--- Quote from: oBFusCATed on November 23, 2012, 12:20:56 pm ---Morten this commit is useless... r8596, because if you look at the initial log you'll see that the "No stack" string is not present there.
--- End quote ---
Maybe for this, but in general it fixes the same show-stopper as this "Function out of bounds". this messages appears if you step deeply into somehow "special" Win32 apps and freeze the debugger. So the fix might not solve this, but another problem. That's why I committed anyways.
BUT: In one of the logs provided here I saw that message at the end, btw...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version