User forums > Using Code::Blocks
64-bit register values and SIMD
bootstrap:
--- Quote from: jens on February 25, 2012, 09:03:58 am ---apt-get update does not update the software, it only updates the package cache.
By the way, debugger-branch is now 7845.
You can try apt-get upgrade to update your system, but I recommend a package manager with a gui, like synaptic .
--- End quote ---
When I run codeblocks it says "svn7844" in the startup dialog and in the "help->about" dialog.
However, the register window still only displays 32-bit hexadecimal values for the registers, though the decimal values do reflect the full 64-bit values. However, the decimal values aren't much use for looking for bits and bit-fields, or for displaying address ranges in memory. Are you saying this SHOULD be fixed in svn7844, but I'm the only one it doesn't work for?
However, I still have the NEW problem that the disassembly window doesn't display anything when I "run to cursor" or "single step". However, the disassembly window DOES fill up with contents when I "step into" a function. I never had a problem with the disassembly window in the original vanilla 10.05 release.
oBFusCATed:
If you have "Settings -> Debugger..." and "Debug->Active debuggers" menus then you have the debugger's branch version.
About the bugs:
1. Yes, it seems the cpu registers window uses 32 bit numbers for the hex values
2. You'll have to show a simple example code and the exact steps, so we can reproduce the disassembly problem. It seems to work correctly here.
Edit:
--- Code: ---Index: src/src/cpuregistersdlg.cpp
===================================================================
--- src/src/cpuregistersdlg.cpp (revision 7856)
+++ src/src/cpuregistersdlg.cpp (working copy)
@@ -66,7 +66,7 @@
}
wxString fmt;
- fmt.Printf(_T("0x%x"), (size_t)value);
+ fmt.Printf(_T("0x%lx"), /*(size_t)*/value);
m_pList->SetItem(idx, 1, fmt);
fmt.Printf(_T("%lu"), value);
m_pList->SetItem(idx, 2, fmt);
--- End code ---
This patch seems to fix it, I've tried it on 64bit linux only.
Jenna:
--- Quote from: bootstrap on February 27, 2012, 09:06:39 am ---When I run codeblocks it says "svn7844" in the startup dialog and in the "help->about" dialog.
--- End quote ---
--- Quote from: jens on February 24, 2012, 06:40:45 am ---7844 is not the debugger branch, as you have written yourself (highlighting by me):
--- Quote from: bootstrap on February 23, 2012, 01:49:03 am ---[...] I should put the following into my ubuntu64 /etc/apt/sources.list file:
deb http://apt.jenslody.de/ any dbg
deb-src http://apt.jenslody.de/ any dbg
[...]
--- End quote ---
you should not use the main, but the dbg section !
[...]
--- End quote ---
--- Quote from: jens on February 25, 2012, 09:03:58 am ---By the way, debugger-branch is now 7845.
--- End quote ---
But if I understand oBFusCATed correctly it does not work there at the moment.
bootstrap:
Looks like now I can't figure out how to make ubuntu64 install the debug branch. I *have* replaced those lines in the sources.list file and updated, but I guess I still have the main branch. Is it now impossible to get the debug branch due to version numbering or something?
As for the disassembly window not showing contents, I generally start running with "run to cursor".
Another question. Is it supposed to be possible to change register values while at a breakpoint? I can't seem to find a way, but other debuggers I've seen (and written) allow that.
When I ran synaptic, I couldn't figure out how to get it to do anything sensible. Any simpler ways that actually (horror) becoming expert at synaptic.
oBFusCATed:
--- Quote from: bootstrap on February 27, 2012, 12:31:45 pm ---As for the disassembly window not showing contents, I generally start running with "run to cursor".
--- End quote ---
Exact steps, please, but first make sure you have the debugger's branch. There were some fixes in regard to the disassembly.
--- Quote from: bootstrap on February 27, 2012, 12:31:45 pm ---Another question. Is it supposed to be possible to change register values while at a breakpoint? I can't seem to find a way, but other debuggers I've seen (and written) allow that.
--- End quote ---
In debugger's branch you can execute gdb commands, there is an entry box at the bottom of the debugger log.
Only you'll have to learn what are the exact gdb commands. I guess there is a room for improvement here :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version