User forums > Nightly builds
The 21 August 2010 build (6508) is out.
oBFusCATed:
--- Quote from: Ceniza on August 22, 2010, 03:48:36 pm ---The disassembly window did not work (all I got was ?? and no instructions).
--- End quote ---
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.
--- Quote from: Ceniza on August 22, 2010, 03:48:36 pm ---The "Debug->Debugging windows" menu does not show the windows that are currently opened while debugging.
--- End quote ---
Works, too...
Can you post a screenshot?
--- Quote from: Ceniza on August 22, 2010, 03:48:36 pm ---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.
--- End quote ---
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...
Ceniza:
--- Quote from: oBFusCATed on August 22, 2010, 04:03:04 pm ---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.
--- End quote ---
--- Quote ---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:
--- End quote ---
--- Quote ---Works, too...
Can you post a screenshot?
--- End quote ---
At first no window was ticked. I clicked on "Watches" (which was already visible), and it go its tick. Disassembly window was not shown. I clicked on it, I got it, and the tick was also there. CPU Registers was shown from the beginning, never clicked it, never got the tick.
--- Quote ---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...
--- End quote ---
I will see if I can get it from the existing ones.
[edit]
Proposed icons attached.
[/edit]
oBFusCATed:
Hm, the disassembly command is not executed...
--- Code: ---> 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
........
--- End code ---
Probably the regex doesn't match in:
--- Code: ---class GdbCmd_DisassemblyInit : public DebuggerCmd
{
...
...
void ParseOutput(const wxString& output)
{
cbDisassemblyDlg *dialog = Manager::Get()->GetDebuggerManager()->GetDisassemblyDialog();
if (reDisassemblyInit.Matches(output))
{
--- End code ---
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?
I've to restart to windows to do some testing there, on linux I've no problems with the checks :(
oBFusCATed:
--- Quote from: Ceniza on August 22, 2010, 04:29:17 pm ---[edit]
Proposed icons attached.
[/edit]
--- End quote ---
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.
Ceniza:
--- Quote from: oBFusCATed on August 22, 2010, 05:24:40 pm ---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?
--- End quote ---
Changing that regex fixes the issue, but I cannot see in which instruction the program actually is.
I also tried 10.5, and it has the same initial problem (empty window).
--- Quote from: oBFusCATed on August 22, 2010, 05:31:01 pm ---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.
--- End quote ---
I do not like the "Next line" icon. It gives the idea that it skips something. I would prefer to change that one instead to something like <see attached>.
I also think rearranging the buttons like that is a good idea. What I find nice about Visual Studio is that 'instruction' debugging is mixed with C/C++ code in an editor window, so the step and next buttons work in instruction mode when that is the active editor. I hope we can get to mixed mode some day (all functionality is in GDB already).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version