STUB in COM:
http://dev.9cbs.net/Article/20/20783.shtm
http://comcamp.myrice.com/techarticles/vc/0005.htm
In the test, Stub sometimes means "piling procedures" (it should be implanted), but in COM is still a root solution.
STUB in RMI:
http://www.nihaoblog.com/143_2154.html
http://www.csip.cn/new/st/jvl/2004/1224/3841.htm
STUB in GDB:
GDB use details
When you debug a remote target device, GDB rely on a debug stub to complete its function. Debug STUB is a small piece of code in an embedded system, which provides a medium between the host machine and the debugged application running GDB. GDB and debug STUB communicate via GDB serial protocol. The GDB serial protocol is a message-based ASCII code protocol that includes commands such as read and write memory, query registers, running programs. Because most embedded system designers have written their own stubs in order to make specific hardware features in their hands. So we need to understand the GDB serial communication protocol. In the back, we will introduce
http://www.hhcn.org/gdb.html
Use GDB debug embedded system
Host debugger
On the host site, you will have to need a GDB version to be used as a debugger for the target processor. The GNU GCC tool provided by the seller should accompany a compiled executable GDB, otherwise you must download the source code from the RedHat or need a GNU FTP, then build the debugger yourself. If you want to run a Linux host or a Windows Cygwin, the establishment of the debugger is a relatively simple process.
Target "Stump"
The GDB debugger communicates with a small "stump" running on the target processor. The host debugger communicates with a protocol that uses simple support read and write registry and memory. You will find a "stump" with many processor systems in the GDB source directory, such as Sh-stub.c, i386-stub.c, and m68k-stub.c.
If you don't find a suitable "Stump", check the GDBSTubs project on SourceForge. You need to compile and connect the appropriate "Stump" to the target embedding and provide two communication functions: getDebugchar () and PUTDEBUGCHAR (). Your system initialization code also calls the set_debug_traps () function to initialize the "stump" and the necessary debug abnormality processing.
Write your own "stump"
If you can't find a "stump" that has been written, you have to write your own "stump" yourself. If you are familiar with the target CPUX system, such projects are not very complicated. The easiest way is to make changes to the ready "Stump". The vast majority of the code in the "Stump" is related to the communication protocol, which can be used unchanged between different processors.
You will need to change the contigable program part, which mainly handles anomalous problem for installation and processing processors, including breakpoints, single step, and generic protection errors.
Abnormal processing is relatively simple: they must register the CPU in a static buffer, then enter the Handle_exception () function, which has an integer parameter displaying an abnormal cause. The Handle_Exception () function then acquires control of the CPU and processes all communication with the host debugging section. You will need some of the Handle_Exception () function, but most of the code can be utilized.
Http://www.zdnet.com.cn/developer/webdevelop/story/0,3800067013,39156474,00.htm
Debugging skill analysis using ROM monitor
Redboot comes with a GDB "Stub)" that provides a target-end communication software that allows users to perform remote debugging through standard GDB protocol commands, so designers can use Redboot and hosts running the GNU debugger through serial port or network. Connect to debug design embedded software. Redboot supports a variety of processor architecture and hardware platforms, including ARM, Hitachi SHX, MIPS, PowerPC, SPARC, and X86. http://www.eetchina.com/art_8800312705_617693_7fccc601.htm
STUB in unit test:
1. Drive Module: The main program equivalent to the measured module. It receives test data to transmit these data to the measuring module, and finally output the actual test results. 2. Pile Module (STUB): Used to replace the submodule called by the module. The pile module can do a small amount of data operation, do not need to bring all the functions of the sub-module to, but do not do anything. The measuring module consists of its related drive module and the pile module constitute a "test environment". The writing of the drive module and the pile module will bring additional overhead to the test. Because they are not delivered as part of the product when software delivery, and their writing requires a certain amount of work. In particular, the pile module cannot simply give information about "once enters". In order to be able to get the correct test software, the pile module may need to simulate the function of the actual sub-module, so that the establishment of the pile module is not very easy.
http://www.matrix.org.cn/forum_view.asp?forum_id=18&view_id=17561
Other stub
STUB sometimes it is also the meaning of tap
