From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Billalabeitia, Jose Carlos (IndSys, GEPM)" <jc.billalabeitia@indsys.ge.com>
To: gdb@sourceware.cygnus.com
Subject: Tracepoints
Date: Wed, 11 Jul 2001 10:38:00 -0000
Message-id: <A1C99F4731CAD111BA5400A024FC3B0C9DB1C0@ESBILMA01EDCGE>
X-SW-Source: 2001-07/msg00096.html

	Hi everybody:

	First of all, my system consists of a custom PowerPC860 board, 
connected to a BDI2000 emulator, through BDM:
	
	BDI Type  : BDI2000 Rev.C
	Loader     :  V1.05
	Firmware :   V1.08 bdiGDB for MPC8xx
	Logic       :  V1.02 MPC8xx/MPC5xx

On the other hand, the BDI2000 is connected to a
Linux PC Host through the Ethernet port. In the host, I have DDD
v3.3 as the graphical debugger and gdb 5.0 as the inferior debugger.

	Up to now I can run properly all the features that DDD offers,
but tracepoints are only supported by the gdb-5.0 not by DDD in this
version, so I have to setup the tracepoints through the DDD-gdb console.
The problem comes when trying to set up the tracepoints:

(gdb)trace board.c:158	 (Here I setup a tracepoint in the code)
Tracepoint 1: file board.c line 158
(gdb)actions 1 (Here is where I should set up the variables to be recorded)
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
> 1
warning: '1' is not an action that I know, or is ambiguous
......
...... (Here I have to press ^C to quit)
^CQuit
(gdb)tstart	(Here I want to start tracing)
Target does not support this command
(gdb)tstop	(Here I want to stop tracing)
Target does not support this command
(gdb)tfind tracepoint 1	(Here I want to see the recorded values off-line)
Target does not support this command 
	

	My thinking is that this feature doesn´t depend on the 
hardware (???) but on the gdb. The gdb seems to be executing 
some instructions consecutively and in a automatic way:

	- stops the program at the tracepoint
	- records variables, registers, ... (snapshots)
	- stores them
	- continues to run the program

My questions are:

	- Is there something wrong in what I do, in the gdb console?
	- Are the tracepoints implemented in the BDI2000 gdbserver?
	- Does it depend on the BDI2000 software version?
	- Is there any other way of getting the same functionality as with
	  the tracepoints, apart from backtrace?
	- Do you know how other people work to get this functionality?
	- Is there a DDD version that supports tracepoints?

						Thank you in advance
							Billa