This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

run-mode debugging with eCos and GDB?


I am evaluating RTOS' for a new project and am coming from a commercial RTOS
background (VxWorks, ThreadX) where those systems offered what is known as
run-mode debug.  In this mode, a specific thread is the focus on the
debugging activity and a breakpoint in that thread suspends the thread while
leaving all other threads running.  This mode contrasts with halt-mode
debugging where a breakpoint halts the entire processor and therefore all
threads stop.  Run-mode debugging is extremely useful/necessary for
development where we are managing external activities that cannot be stopped
(such as software flow control of incoming data streams).

eCos is a contender for this new project but it is not clear to me if
"thread awareness" of GDB with eCos means that ability to display thread
specific information AND is also equivalent to run-mode debugging, or it is
merely the display of thread information.  The bottom line is, when
debugging in eCos and GDB do all application tasks suspend or merely the
targeted thread?

Thanks

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]