User forums > Nightly builds
The 24 August 2010 build (6527) DEBUGGER BRANCH version is out.
killerbot:
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml
Before you use a nightly make sure you understand how it works.
A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2810_gcc441.7z
For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc441.7z
The 24 August 2010 build is out.
- Windows :
http://prdownload.berlios.de/codeblocks/CB_20100824_rev6527_DEBUGGER_BRANCH_win32.7z
- Linux :
none
Important changes compared to regular nightly:
* The stop button was split to pause and stop
* New watches window using wxPropGrid
* Rename the watch with the Insert key (don't work on windows, some help will be appreciated)
* Delete key in Breakpoints window deletes the selected breakpoint
* Drag/drop from the editor to the watches window
* Made adding watches from the context menu in the editor to be easier: select some text -> right click -> add watch
* The evaluate tooltip should not show outside the editor window, also should not show if you move the mouse from the initial position
* Added "Set next statement command", please use with care and understanding ( http://sunsite.ualberta.ca/Documentation/Gnu/gdb-4.18/html_node/gdb_93.html )
* Switch to frame does work now (added option to make double clicking switch to frame or jump to frame in the call stack window)
* Fixed bug https://developer.berlios.de/bugs/?func=detailbug&bug_id=16146&group_id=5358
* Fixed bug 13972 ( http://developer.berlios.de/bugs/?func=detailbug&bug_id=13972&group_id=5358 )
* If the build fail a message box is shown "Build failed. Do you want to debug, anyway?", it is useful for debugging unittest projects that have failing tests
* Attaching and detaching should work better (BUG: attaching to codeblocks doesn't at the moment)
* Ensure visible the selected/active frame in the backtrace window
* Run host it terminal ( Project -> Set programs' arguments)
* Close the console when the user unloads the project/closes C::B, while the debugger is running
* Clicking on a frame that points to a missing file now shows an info window with the error message
* Catching exceptions should work now
* Added command to disable the feature of gdb to shorten the lines in the output from commands.
This should improve the reliability of the plugin.
Note: Watch parsing prints an error message in the watches window if the parsing fails. If you see this string please report it as a bug.
THIS IS A SPECIAL TEST BUILD OF REFACTORINGS CARRIED OUT ON THE DEBUGGER BRANCH IN OUR SVN.
FOCUS IS ON ENHANCED DEBUGGING USABILITY.
Give your feedback on this version only in this thread, don't mix it with the regular nightly please.
Once we don't have any blockers on this version,we will merge the changes into trunk and it will be part of the regular nightlies.
oBFusCATed:
Some notes:
1. Please look for regressions! A regression is a bug that is not present in the regular nightly, but present in this one.
Only regressions will be blockers (I think:) )
2. When you find a bug, please paste the debugger's debug log ( Settings -> Compiler & Debugger -> Debugger -> Display debugger's log ).
Please use code tags, in order to keep the readability of your posts.
3. I think GCC >=4.5.x requires GDB 7.0+, so if you're using this version of GCC please update your GDB
Known problems:
1. Local variables are not shown in the watches window.
Reason: I wanted to move them to separate window, but wxAUI doesn't support moving windows from on notebook to another,
so I've just removed them and I'm waiting wx guys to implement this feature (go bug them on their mailing list :) )
2. Function arguments are not shown in the watches windows.
Reason: same as above
killerbot:
can we have in the watches window, several tabs (kind of like in the project management window), we could have a tab with manual added watches, and one with function arguments and locals.
We could even have a second tab with manual added watches ;-) [I think MSVC has this]
oBFusCATed:
Yes, we can, wxPG supports pages (see the wxPG in the wxSmith), but I don't like them solution...
MSVC has Watches1, Watches2, Watches3,Watches4, Autos, Locals, but they can dock any window inside any notebook/zone, it is pretty powerful...
killerbot:
well it could be a temp solution until you can implement the functionality like you prefer once wx dev's have added what you want. The latter could take some time I guess. The former could enhance the debugging experience in the short term ?
Navigation
[0] Message Index
[#] Next page
Go to full version