User forums > Nightly builds
The 26 January 2008 build (4845) is out.
@nthony:
In the symbols browser of the Manager tab "Jump to declaration" and "Jump to definition" do not do either (nor does double-clicking the item).
stahta01:
To compile trunk using windows XP and NOT using PCH needed this patch.
Tim S
--- Code: ---Index: src/plugins/classwizard/classwizarddlg.cpp
===================================================================
--- src/plugins/classwizard/classwizarddlg.cpp (revision 4852)
+++ src/plugins/classwizard/classwizarddlg.cpp (working copy)
@@ -41,6 +41,7 @@
#include "editormanager.h"
#include "globals.h"
#include "manager.h"
+#include "macrosmanager.h"
#include "projectmanager.h"
#endif
#include "cbstyledtextctrl.h"
--- End code ---
killerbot:
done
rhf:
I have just experienced a problem with the latest nightly build on Windows XP.
The debug commands are not working properly. For example, F7 does not do Next Line but does Step into, which should be Shift-F7. Ctrl-Shift-F7 appears to abort or maybe continue, etc.
I then tested this with my compiled CodeBlocks and had similar problems, so this may not really be a Nightly build problem.
Everything looks OK in cbKeyBinder10.ini. I also tried an earlier gdb.exe with no luck. It is possible that I messed up the .conf file but I have erased it and started over several times with no success.
This is bad timing because I was using the latest Nightly build to convince several colleagues to switch to CodeBlocks.
Their first question was, does CB have an integrated debugger. Hopefully, someone has a simple suggestion for fixing this before my colleagues give up on me.
Thanks.
Pecan:
--- Quote from: rhf on January 30, 2008, 06:45:32 pm ---I have just experienced a problem with the latest nightly build on Windows XP.
The debug commands are not working properly. For example, F7 does not do Next Line but does Step into, which should be Shift-F7. Ctrl-Shift-F7 appears to abort or maybe continue, etc.
I then tested this with my compiled CodeBlocks and had similar problems, so this may not really be a Nightly build problem.
Everything looks OK in cbKeyBinder10.ini. I also tried an earlier gdb.exe with no luck. It is possible that I messed up the .conf file but I have erased it and started over several times with no success.
This is bad timing because I was using the latest Nightly build to convince several colleagues to switch to CodeBlocks.
Their first question was, does CB have an integrated debugger. Hopefully, someone has a simple suggestion for fixing this before my colleagues give up on me.
Thanks.
--- End quote ---
As a test, I would completely disable keybinder at Menu/Plugins/ManagePlugins. Then restart CB.
If that solved the problem, I'd then delete keybinder10.ini . Keybinder will build a new one on the next CB startup.
It's possible that a crash or very old keybinder10.ini file has mismatched the menuId's. I've seen this happen when a plugin crashes while keybinder was writing it's .ini file.
It's also possible, that if you've copied a keybinder ini file that belonged to a different configuration of CB (eg., different plugins loaded) that the menuId's will be off by the number of menu items the plugins add or replace. Eg., plugin y on system2 got system1's plugin x's menuId's from the copied keybinder10.ini, because plugin x is not on system2.
This corrects itself over time (in partial scans every 15 seconds), but it can be confusing.
To make a new keybinder10.ini, simple (re)"save" after bringing up the keybinder settings dialog.
Edit: 2008/01/30 1:44
My F7 and other debugger keys seem to be working correctly.
svn build rev 4829 (2008-01-16T20:17:30.273085Z) gcc 3.4.5 Windows/unicode
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version