Studio:Integrating the Intercept Module (IM) - Revision history

Ivailop: /* IM Resource Requirements */

2010-05-19T23:00:58Z

IM Resource Requirements

← Older revision		Revision as of 23:00, 19 May 2010
Line 13:		Line 13:
	=== IM Resource Requirements ===		=== IM Resource Requirements ===
	The Intercept Module is usually run as a separate task, and therefore has some		The Intercept Module is usually run as a separate task, and therefore has some
	resource requirements that are in addition to those of the [[~~Target~~ Integration~~#The~~ STRIDE Runtime ~~\|Runtime]] and the [[Target Integration#The Platform Abstraction Layer (PAL)\| PAL~~]]. One of these is the task resource itself. Another is space for the task stack.		resource requirements that are in addition to those of the [[Runtime Integration\|STRIDE Runtime]]. One of these is the task resource itself. Another is space for the task stack.

	The required task stack size if difficult to predict since it is dependent on the underlying system and on the data that is passed through function arguments. A stack size between 2-4K would be a good starting point.		The required task stack size if difficult to predict since it is dependent on the underlying system and on the data that is passed through function arguments. A stack size between 2-4K would be a good starting point.

Ivailop: /* Starting the IMStubRead threads */

2010-05-10T20:23:20Z

Starting the IMStubRead threads

← Older revision		Revision as of 20:23, 10 May 2010
Line 22:		Line 22:
	Look at any of the prepackaged [[:Category:SDKs\|SDKs]] for examples of integrating your application.		Look at any of the prepackaged [[:Category:SDKs\|SDKs]] for examples of integrating your application.

	~~[[Category: Installation]]~~
	[[Category:Studio:Installation]]		[[Category:Studio:Installation]]

Timd: Added tag: 'Studio:Installation'

2009-08-20T22:38:15Z

Added tag: 'Studio:Installation'

← Older revision		Revision as of 22:38, 20 August 2009
Line 23:		Line 23:

	[[Category: Installation]]		[[Category: Installation]]
			[[Category:Studio:Installation]]

Timd: Integrating the Intercept Module (IM) moved to Studio:Integrating the Intercept Module (IM)

2009-08-18T21:47:45Z

Integrating the Intercept Module (IM) moved to Studio:Integrating the Intercept Module (IM)

← Older revision	Revision as of 21:47, 18 August 2009
(No difference)

Ivailop: /* Compiling the IM */

2009-03-24T19:23:19Z

Compiling the IM

← Older revision		Revision as of 19:23, 24 March 2009
Line 9:		Line 9:
	cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c		cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c

	Notice that the IM.c and IMEntry.h files reference header files in the STRIDE installation directory. The build must include this directory when compiling either of these files. The ~~Delegate~~ (IM.h) header file does not have any dependencies on this directory.		Notice that the IM.c and IMEntry.h files reference header files in the STRIDE installation directory. The build must include this directory when compiling either of these files. The public interface (IM.h) header file does not have any dependencies on this directory.

	=== IM Resource Requirements ===		=== IM Resource Requirements ===

Ivailop: /* Compiling the IM */

2009-03-24T18:37:18Z

Compiling the IM

← Older revision		Revision as of 18:37, 24 March 2009
Line 6:		Line 6:
	== Activating the Intercept Module ==		== Activating the Intercept Module ==
	=== Compiling the IM ===		=== Compiling the IM ===
	To compile the IM, you must define the '''STRIDE_ENABLED''' (or '''srIMON''' 3.0.01xx or older releases) preprocessor directive when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:		To compile the IM, you must define the '''STRIDE_ENABLED''' (or '''srIMON''' in 3.0.01xx or older releases) preprocessor directive when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:
	cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c		cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c

Ivailop: /* Compiling the IM */

2009-03-24T18:36:57Z

Compiling the IM

← Older revision		Revision as of 18:36, 24 March 2009
Line 6:		Line 6:
	== Activating the Intercept Module ==		== Activating the Intercept Module ==
	=== Compiling the IM ===		=== Compiling the IM ===
	To compile the IM, you must define the '''STRIDE_ENABLED''' (or '''srIMON''' ~~in previous then~~ 3.0.~~0201~~ releases) preprocessor directive when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:		To compile the IM, you must define the '''STRIDE_ENABLED''' (or '''srIMON''' 3.0.01xx or older releases) preprocessor directive when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:
	cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c		cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c

Ivailop: /* Activating the Intercept Module */

2009-03-24T18:35:58Z

Activating the Intercept Module

← Older revision		Revision as of 18:35, 24 March 2009
Line 6:		Line 6:
	== Activating the Intercept Module ==		== Activating the Intercept Module ==
	=== Compiling the IM ===		=== Compiling the IM ===
	To compile the IM, you must define the ~~macro~~ '''srIMON''' when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:		To compile the IM, you must define the '''STRIDE_ENABLED''' (or '''srIMON''' in previous then 3.0.0201 releases) preprocessor directive when you compile the IM.c file or any file that includes one of the headers. This "turns on" the intercept feature. For example:
	cc -c -IC:\STRIDE\inc -~~DsrIMON~~ MyProjectIM.c		cc -c -IC:\STRIDE\inc -DSTRIDE_ENABLED=1 MyProjectIM.c

	Notice that the IM.c and IMEntry.h files reference header files in the STRIDE installation directory. The build must include this directory when compiling either of these files. The Delegate (IM.h) header file does not have any dependencies on this directory.		Notice that the IM.c and IMEntry.h files reference header files in the STRIDE installation directory. The build must include this directory when compiling either of these files. The Delegate (IM.h) header file does not have any dependencies on this directory.

Ivailop: /* Starting the IMStubRead threads */

2008-12-09T00:01:22Z

Starting the IMStubRead threads

← Older revision		Revision as of 00:01, 9 December 2008
Line 20:		Line 20:
	The IM must be started ''after'' the Runtime and Transport have been initialized, but before any intercepted calls can be made. Failure to do this before making an intercepted call can crash or hang the target.		The IM must be started ''after'' the Runtime and Transport have been initialized, but before any intercepted calls can be made. Failure to do this before making an intercepted call can crash or hang the target.

	Look at any of the prepackaged ~~SDKs (~~[[~~Linux SDK]], [[WinMobile SDK~~]]~~...)~~ for examples of integrating your application.		Look at any of the prepackaged [[:Category:SDKs\|SDKs]] for examples of integrating your application.

	[[Category: Installation]]		[[Category: Installation]]

Ivailop at 22:25, 8 December 2008

2008-12-08T22:25:50Z

← Older revision		Revision as of 22:25, 8 December 2008
Line 17:		Line 17:
	The required task stack size if difficult to predict since it is dependent on the underlying system and on the data that is passed through function arguments. A stack size between 2-4K would be a good starting point.		The required task stack size if difficult to predict since it is dependent on the underlying system and on the data that is passed through function arguments. A stack size between 2-4K would be a good starting point.

	=== Starting the ~~srThread and~~ IMStubRead threads ===		=== Starting the IMStubRead threads ===
	The IM must be started ''after'' the Runtime and Transport have been initialized, but before any intercepted calls can be made. Failure to do this before making an intercepted call can crash or hang the target.		The IM must be started ''after'' the Runtime and Transport have been initialized, but before any intercepted calls can be made. Failure to do this before making an intercepted call can crash or hang the target.

	This code snippet for Linux, based on using the POSIX call pthread_create() to start a task (your OS may use a different call), demonstrates how to initialize the PAL and the Runtime, start the IM, then becomes the Runtime message processing loop. Note that this code assumes that it will become the Runtime thread's message processing loop (because srThread() will never return unless thread is stopped or killed). The comments note that this could instead create a second task for the Runtime and return.		Look at any of the prepackaged SDKs ([[Linux SDK]], [[WinMobile SDK]]...) for examples of integrating your application.

	~~=== Implementation ===~~
	Look at any of the prepackaged SDKs ([[Linux SDK]], [[WinMobile SDK]]...) for examples of integrating your application ~~with the STRIDE Runtime~~.

	[[Category: Installation]]		[[Category: Installation]]