| Home | Terms of Use | Site Map | Contact Us |
IndustryCommunity.com > Electrical and Electronic Community > Embedded Control Forum > Message
Main Menu

[ List Subjects ][ Post Message ]
[ View Followups ][ Post Followup ]

Subject: VxWorks debugger ( CrossWind ) query.

Date: 10/11/01 at 3:25 AM
Posted by: Milan Jain
E-mail: milanj@delhi.tcs.co.in
Message Posted:

In the VxWorks debugger ( CrossWind ), there are 2 modes of debugging. The default mode is the 'Task Mode' wherein execution stops at breakpoints of only 1 task even if the user has set breakpoints in other tasks. This task has to be specified by the user.

The second mode is the 'System-mode' debugging. This is the standard mode of debugging found in most other RTOSs wherein execution WILL stop upon encountering any breakpoints, regardless of the task it is in. Now, since this is not the default mode, we have to set the debugger to this mode ( using a number of commands....e.g. Attach->System ).

Now, the question I have is that how do we specify the starting task / function; the "main()" as it were. Typically, one does a "Run" and specifies the starting point. But the problem with this approach is that debugger attaches itself to this task and we are implicitly taken back to the 'task-mode' of debugging.

Also note that we are attempting to build a downloadable image, and NOT a bootable one. So, the "userappinit.c" is NOT part of the project.

Follow Ups:

Post a Follow-up:


Message to Post:


1999-2001 Sunlit Technology Co., Ltd. All rights reserved.