How can I debug an omnet++ project like as a bmac or Imac.
My omnet++ is Version: 4.6 I want to debug an bmac project. Do I need to change any configuration of my simulator?
I will be thank full to have the solution.
Your question is somewhat broad. If, by debugging a simulation you mean running your simulation in a debugger like gdb, see this other answer.
For general tips on debugging in the sense of finding errors, you might find this article on the OMNeT++ wiki helpful.
Related
I have a project for Xilinx Zynq (Cortex A9). I want to be able to step-by-step debug the application in KDevelop. I know that xilinx has XSCT but I don't understand how can I get KDevelop to work in step-by-step code debugging mode for my processor?
I can advise you to learn how to do this from the terminal first and deal with the work of gdb-server. And also get a suitable make/cmake file.
I'm making a wxWidget application for windows. I'm working with code:blocks 13.12 and MinGW 4.8 in windows 7.
I enable the -pg option in settings->compiler and after compiling try to open the plugins->code profiler and the result is this:
gprof:
file`C:\Users\josele\Documents\C_C++\DLL\SQLManager\bin\Release\SQLManager.exe'
has no symbols
Basicly I don't know how profiling works in code:block and also my general knowledge of profiling is quite reduced.
I'm looking for solve this or a tutorial of: how profiling works in code:blocks?.
If you need more information, only let me know. Thank you in advance.
PD. I also run the .exe before calling the plugins->code profiler with a positive exit of the program
I just solve that problem with this posts:
http://forums.codeblocks.org/index.php?topic=12237.0
http://forums.codeblocks.org/index.php?topic=14798.0
I went to Project->build options and there I turn off optimizations and enable the pofiler.
What solved it for me was turning off the "-s" compiler flag, which seems to be on by default in CB release flags.
I've been working on some code for some time now (bitcoin's source code), the building system is GNU Autotools.
I'm having some problems debugging the code. I'm working with eclipse on OSX Mavericks, building the project works great but when i go to debugging prospective i'm having some problems:
Many breakpoint cannot be installed
Some breakpoints that can be installed cause a source not found error
Cannot debug header files
A specific example is when i'm trying to debug step-by-step some of the unit tests, i can't seem to be able to step in functions.
I did: ./configure --with-miniupnpc --enable-upnp-default --with-qrencode --enable-debug so to include debugging flags.
Anyone care to share how he setup his workspace or how to resolve those problems ?
ANYONE ???
i am debugging c++ with eclipse on a linux VM.
The eclipse I am using is Kepler Service Release 1.
I compile the files using Automake.
When I try to debug in Eclipse and do stepover it sometimes jump to backward lines, sometimes it goes into the line. Also when there is a problem it just shows nothing. When I try to see variables it doesn't always succeed. It seems the Eclipse behavior is not so good.
I come from Windows programming and it looks very much like I saw when we compiled release version and tried to debug it in Visual.
Can anyone plesae assist? I can't debug like this. Is there any configuration? something I do wrong?
Thanks
As Martin James stated all I needed was to turn off all optimizations.
I had -o2 flag and needed to remove it.
I am encountering the same problem that many others have in Eclipse, as is apparent by the many questions. I found an answer in [this question] (How can I enable breakpoints in Eclipse/CDT)
So I checked my Run-->Breakpoint Types and there were none available. How do I change that?
BTW: I don't believe this should matter, but I have set up my Eclipse project by hand and added the CMake files. I have to run CMake to generated dependencies in the code. But by creating my Eclipse project by hand I should be able to debug it. So, again, how do I add Breakpoint Types?
Thank you.
I hate it when I post a question and then find the answer!
I fixed this problem by following the instructions in the Eclipse Community Forums Question, which took me to CDT/User/FAQ Eclipsepedia - Enable the C/C++ Tracepoint functionality that told me what to do.
It worked! Yay! I hope this information helps others.