User forums > Embedded development

[solved]remote debug on arm

<< < (3/3)

cermakpe:
There is small different problem.
If you does not support exeptions in arm C++ debugged code this crash appear. You must check off Catch C++ Exeption in Debugger Tab.
This crash is due to gdb finish before line 1550 in debugergdb.cpp
and GetDrive return NULL (no gdb running or finishing before)

in debug window:
"
Building to ensure sources are up-to-date
Build succeeded
Selecting target:
Debug
Adding source dir: /mnt/sdb1/bl/blink/
Adding source dir: /mnt/sdb1/bl/blink/
Changing directory to: bin/Debug
Adding file: bin/Debug/blink
Starting debugger:
done
Running command: set prompt >>>>>>cb_gdb:
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting serial connection speed to 38400
Connecting to remote target
Setting breakpoints
Running command: show version
Running command: set confirm off
Debugger name and version: GNU gdb (eCosCentric GNU tools 4.3.2-sw) 6.8.50.20080706
Running command: set width 0
Running command: set height 0
Running command: set breakpoint pending on
Running command: set print asm-demangle on
Running command: set unwindonsignal on
Running command: set disassembly-flavor arm7tdmi
Running command: catch throw
Debugger finished with status 1
"
and Crash...


Solving:

    // Don't issue 'run' if attaching to a process (Bug #1391904)
    if (m_PidToAttach == 0)
   // in case finish gdb with result 1 (Catch C++ exeptions setting), GetDriver() return NULL
        if( m_State.GetDriver() != NULL)
      m_State.GetDriver()->Start(m_BreakOnEntry);

    // switch to the user-defined layout for debugging
    if (m_pProcess)
        DoSwitchToDebuggingLayout();
 
Best
Petr Cermak. :D

oBFusCATed:
Can you try the latest debugger's branch nightly and report back if the problem is still there?

Keep in mind that trunk is frozen in regard to changes in the debugger, all development happens in the branch...

martind:
Hi,

I am the developer of the plugin you have mentioned. I have not done much work on it recently but am now back on it as I have been looking at the whole architecture of the plugin.

I have found an issue with CodeSourcery also when you are debugging, where each step causes the debugger to advance by 2 steps. It's something I have been meaning to look at but again have not made the time.

The variables cb relates to the source directory of CodeBlocks, and wx is the wxWidgets directory. Thats all you should need.

I have been debugging with CB and OpenOCD (with the cbmcu plugin) for some time using the Yagarto compiler: http://www.yagarto.de/



Regards,


Martin.

Navigation

[0] Message Index

[*] Previous page