User forums > Help
Breakpoint Being Ignored <with full debugger log>
oBFusCATed:
--- Quote from: dcbdbis on December 14, 2013, 04:57:12 am ---I think you may have a hunch where to look in the code.....Can you please give me a heads-up on which of the source files you pointed me at, where the whole debugger gets called and integrated into C::B?
--- End quote ---
BlueHazzard gave you the link to the files, debuggergdb.cpp is the main one.
But I don't think the problems is inside the debugger plugin. It is related to the initialization of something that has a data-race or something like that, but I don't know what.
dcbdbis:
--- Quote ---It is related to the initialization of something that has a data-race or something like that, but I don't know what.
--- End quote ---
Ok, I understand. Now that I know where all the source code resides... It seems that I need to look at the section of C::B that initiates the debugger. I will now turn my attention to the code and the browser framework and start to look. No promises...but the more eyes that are looking at this problem.....the sooner we'll all find it!
Thanks!
Sincerely,
Dave
dmoore:
--- Quote from: dcbdbis on December 14, 2013, 07:27:19 pm ---Ok, I understand. Now that I know where all the source code resides... It seems that I need to look at the section of C::B that initiates the debugger.
--- End quote ---
No, this is not a problem with the debugger interface per se. As oBfUsCaTeD showed you, if you open a terminal (e.g. gnome-terminal) from Code::Blocks and start the debugger from the terminal, you will still have this problem. This is most likely a problem with how we call wxExecute or, just as likely, with wxExecute itself.
I have had all kinds of unexpected issues with wxExecute in the past (unrelated to the debugger) where behavior of a process spawned by C::B (or spawned by some process originally spawned by C::B) is very odd.
Also see http://forums.codeblocks.org/index.php?topic=4435.0
dcbdbis:
--- Quote ---This is most likely a problem with how we call wxExecute or, just as likely, with wxExecute itself.
--- End quote ---
Understood, this would mean that this issue may not span across all versions of the wxWidget libary. Has anyone built C::B against wxWidgets 3 or 2.9.* to see if this issue remains across different versions of the wx toolkit?
Sincerely,
Dave
oBFusCATed:
I'm not 100% sure I've tried it against wx29/30. Can you try it and report if it works 100% of the time?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version