FYI : later today a special nightly will be released, containing a special build from our debugger branch. This is basically refactoring done on the debugger features of CB, once we gt proper feedback on this one, this will be merged to trunk and will be available in the regular nightly. Stay tuned ;-)Good job! :)
FYI : later today a special nightly will be released, containing a special build from our debugger branch. This is basically refactoring done on the debugger features of CB, once we gt proper feedback on this one, this will be merged to trunk and will be available in the regular nightly. Stay tuned ;-)
The disassembly window did not work (all I got was ?? and no instructions).Works here, can you paste the gdb output from the debugger's debug log?
The "Debug->Debugging windows" menu does not show the windows that are currently opened while debugging.Works, too...
Add to that that there is a button still missing in the toolbar: step into instruction (stepi). GDB is a really nice debugger, but the front-end in Code::Blocks needs a lot of love.Can you provide an icon, the other part of the job is easy to do? And I'll do it when I've the icon...
Works here, can you paste the gdb output from the debugger's debug log?
The disassembly window works only when you've stopped on a breakpoint.
PATH=.;C:\Program Files (x86)\CodeBlocks\MinGW\bin;c:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW32\bin;C:\Program Files\TortoiseSVN\bin;c:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW32\bin;C:\Program Files\TortoiseSVN\bin;C:\bin
Command-line: C:\Program Files (x86)\CodeBlocks\MinGW\bin\gdb.exe -nx -fullname -quiet -args bin/Debug/EventTest.exe
Working dir : C:\Users\Ceniza\Documents\Visual Studio 2010\Projects\EventTest\
> set prompt >>>>>>cb_gdb:
(gdb) >>>>>>cb_gdb:
> show version
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32".
>>>>>>cb_gdb:
> set confirm off
>>>>>>cb_gdb:
> set width 0
>>>>>>cb_gdb:
> set height 0
>>>>>>cb_gdb:
> set breakpoint pending on
>>>>>>cb_gdb:
> set print asm-demangle on
>>>>>>cb_gdb:
> set unwindonsignal on
>>>>>>cb_gdb:
> set print elements -1
>>>>>>cb_gdb:
> set debugevents on
>>>>>>cb_gdb:
> set new-console on
>>>>>>cb_gdb:
> set disassembly-flavor att
>>>>>>cb_gdb:
> catch throw
Catchpoint 1 (throw)
>>>>>>cb_gdb:
> source F:\Source\codeblocks_dbg\src\output\share\codeblocks/scripts/stl-views-1.0.3.gdb
>>>>>>cb_gdb:
> directory C:/Users/Ceniza/DOCUME~1/VISUAL~1/Projects/EVENTT~1/
>>>>>>cb_gdb:
> directory C:/Users/Ceniza/DOCUME~1/VISUAL~1/Projects/
>>>>>>cb_gdb:
> break "C:/Users/Ceniza/Documents/Visual Studio 2010/Projects/EventsTest/EventsTest/main.cpp:362"
Breakpoint 2 at 0x4014b4: file C:\Users\Ceniza\Documents\Visual Studio 2010\Projects\EventsTest\EventsTest\main.cpp, line 362.
>>>>>>cb_gdb:
> run
gdb: win32_init_thread_list
[New thread 2404.0xb54]
Error: dll starting at 0x76e80000 not found.
Error: dll starting at 0x76b40000 not found.
Error: dll starting at 0x76e80000 not found.
Error: dll starting at 0x76d80000 not found.
Breakpoint 2, main () at C:\Users\Ceniza\Documents\Visual Studio 2010\Projects\EventsTest\EventsTest\main.cpp:362
C:\Users\Ceniza\Documents\Visual Studio 2010\Projects\EventsTest\EventsTest\main.cpp:362:9230:beg:0x4014b4
>>>>>>cb_gdb:
> set debugevents off
>>>>>>cb_gdb:
> info registers
eax 0x28fec8 2686664
ecx 0x76c57712 1992652562
edx 0x41d158 4313432
ebx 0x28fedc 2686684
esp 0x28fe50 0x28fe50
ebp 0x28ff28 0x28ff28
esi 0x28fee8 2686696
edi 0x28febc 2686652
eip 0x4014b4 0x4014b4 <main+384>
eflags 0x202 [ IF ]
cs 0x23 35
ss 0x2b 43
ds 0x2b 43
es 0x2b 43
fs 0x53 83
gs 0x2b 43
>>>>>>cb_gdb:
> info frame
DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
Stack level 0, frame at 0x28ff30:
eip = 0x4014b4 in main (C:\Users\Ceniza\Documents\Visual Studio 2010\Projects\EventsTest\EventsTest\main.cpp:362); saved eip 0x4010b6
source language c++.
Arglist at 0x28ff28, args:
Locals at 0x28ff28, Previous frame's sp is 0x28ff30
>>>>>>cb_gdb:
Works, too...
Can you post a screenshot?
Can you provide an icon, the other part of the job is easy to do? And I'll do it when I've the icon...
> disassemble
Dump of assembler code for function main:
0x0000000000400d6e <+0>: push rbp
0x0000000000400d6f <+1>: mov rbp,rsp
0x0000000000400d72 <+4>: push r12
0x0000000000400d74 <+6>: push rbx
........
class GdbCmd_DisassemblyInit : public DebuggerCmd
{
...
...
void ParseOutput(const wxString& output)
{
cbDisassemblyDlg *dialog = Manager::Get()->GetDebuggerManager()->GetDisassemblyDialog();
if (reDisassemblyInit.Matches(output))
{
[edit]Then next instruction should look more like the next line icon.
Proposed icons attached.
[/edit]
Can you try to replace the
static wxRegEx reDisassemblyInit(_T("^Stack level [0-9]+, frame at (0x[A-Fa-f0-9]+):"));
with:
static wxRegEx reDisassemblyInit(_T("Stack level [0-9]+, frame at (0x[A-Fa-f0-9]+):"));
And I think that disassembly won't work in your normal C::B, can you try that, too?
Then next instruction should look more like the next line icon.
Also, what about a little rearranging:
At the moment we have: Debug, RunToCursor, Next line, Next instruction, Step Into, Step Out, Pause, Stop.
I think the following order is better: Debug, RunToCursor, Next line, Step Into, Step Out, Next instruction, Step into instruction, Pause, Stop.
I will wait with a debugger branch based special nightly, until these first issues are sorted out. PM me when it is good to go.Well - in fact all these work for me, too.
@oBFusCATed: Did you try dwarf2 yet?I'm using gcc 4.4.4 and -g option, so if dwarf2 is the default in this gcc I've tried it.
@Ceniza: It seems you are using dwarf2 instructions? I never tried, but how well does GDB work with this in general...?!
Can you provide a backtrace or crashreport file?sorry no crash report instand close
Also some OS info will come in handy :)
@BloodyCake: I had to check what I am using, and it says it is gcc 4.5.0 (tdm-1). I have no idea how well it works in general, but at least that little test program worked quite nicely with GDB in a console.If you're going to use gcc 4.5.x+ you'll have to upgrade to newer gdb (than 6.8.x).
@oBFusCATed: Is it also part of the refactoring process to move to the mi interface for GDB, is it going to be something for later (once the branch is merged), or is it something yet to consider?GDB/mi is a separate effort, it will result in a new plugin, but I've not worked on it lately (I plan to resurrect it again in the coming weeks)...
Hi,
In this nigthly (and in the previous one) the codesnippet is no longer available. The View->Toolbars has no codesnippet (it had the entry in the past) and the codesnippet.exe is present in the installation directory.
This issue was also reported by several users in the thread related to the previous nightly, but all the reports were ignored. So may be the feature has been removed intentionally.
Please can you clarify?
Regards
Max
The problem comes from the resources zip archive: the file $(CodeBlocks)\share\codeblocks\codesnippets.zip is actually empty (no manifest file). All you have to do is to recover this manifest file in the SVN repository, zip it in codesnippets.zip, and replace the file in the directory $(CodeBlocks)\share\codeblocks (or you can use the file I attach and copy it to $(CodeBlocks)\share\codeblocks)
It works for me.
I do not know the reason why it is so - it is perhaps a mistake, or the plugin is deactivated intentionnaly for a technical reason. Only the devs will be able to answer you.
I'd say its only a mistake. But I am sure killerbot has read this and will take the appropriate steps. There is no reason to remove this plugin, it works just fine.I do not know the reason why it is so - it is perhaps a mistake, or the plugin is deactivated intentionnaly for a technical reason. Only the devs will be able to answer you.Any advice from devs?
View->ToolbarsIt is not in this place, the entry is directly in the View menu, not in the toolbar subsection.