Hi Lai. If you can't convert intel assembler instructions into ARM instructions in your mind, taking all the incorrect mnemonics into account, you'll most likely have problems.
In other words: Your debugger will certainly have to be an ARM debugger in order to show ARM instruction set. But that's not even enough. The disassembled instructions you see would not do what you would expect them to do either. Just like the word "is" in english means "to be", where it means "ice" or "ice cream" in danish. So... Compile a GDB for your platform, which is targeting ARM; if you've ever tried building open-source tools, this one is simple to build: (Don't type the '$' in front of the commands) $ mkdir -p ~/open-source; cd ~/open-source $ tar -xjf gdb-7.6.1.tar.bz2 $ mkdir gdb; cd gdb $ ../gdb-7.6.1/configure --target="arm-none-eabi" --prefix="/usr/local/arm-none-eabi" --disable-nls --enable-sim-arm --enable-sim-stdio $ make -j8 all && sudo pmake install && echo "Success" Love Jens On Thu, 31 Oct 2013 11:37:45 +0800, Lai Quang Vinh (RBVH/ENG2) wrote: > Hi developers, > > Currently, I want to develop a Netbeans module for communicate with > OpenOCD Server. So I may be have to interact with GNU Debugger > Client. But “OpenOCD User’s Guide” said that “the version of GDB you > use will need to be one which has been built to know about the target > CPU you’re using. It’s probably part of the tool chain you’re using. > For example, if you are doing cross-development for ARM on an x86 PC, > instead of using the native x86 gdb command you might use > arm-none-eabi-gdb if that’s the tool chain used to compile your code” > and gave a sample GDB session use arm-none-eabi-gdb debugger. > Because I think that Debugger Client complies with the remote > protocol is enough, so my question is: > Can I use a Common GNU Debugger instead of debugger from tool chain? > Are there problems if I use a Common GNU Debugger? > > Thanks, > Lai Quang Vinh > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk_______________________________________________ > OpenOCD-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openocd-devel ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
