This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
We are currently facing a problem when debugging our linux application using CCS GDB. We are using :
1. GCC Toolchain : gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux
2. CCS Version : v5.5
3. Platform : AM5777 running Linux3.8 on ARM core
4. Application : Multi -threaded C application
Our main application spawns multiple tasks (total of 4) which are dedicated to perform specific activities.
We are able to successfully spawn each of these tasks, but when we put a breakpoint in any of these tasks and try to debug the same ( I mean single stepping the program using F6) using CCS GDB we are not able to control the debugging between various tasks.
What I mean by this is that we are not able to control the execution of each of these tasks individually by single stepping the code. Every time when we try to single step a particular task (by using F6) all the other task spawned also executes in parallel.
Is there any specific option in CCS / GDB which we need to set so that we can control the execution of these tasks ?
Please comment.
Thanks Naveen
Naveen,
If I understand correctly what you are looking for is non-stop mode debugging of multi-threaded programs, (ie) where halting or stepping through one thread does not force other threads to also halt and/or step. The default mode for GDB is all-stop mode, where when one thread stops, then all other threads are also stopped by GDB. There seems to be a setting in GDB to control this which you should be able to set from CCS (Window->Preferences).
Please see the references below. Hope they are helpful.
https://sourceware.org/gdb/onlinedocs/gdb/Thread-Stops.html#Thread-Stops
http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Freference%2Fcdt_u_dsfgdb.htm