From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32621 invoked by alias); 12 Jun 2003 18:15:29 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 32551 invoked from network); 12 Jun 2003 18:15:27 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 12 Jun 2003 18:15:27 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 0B0EBD2DAF; Thu, 12 Jun 2003 11:15:10 -0700 (PDT) Date: Thu, 12 Jun 2003 18:15:00 -0000 From: Joel Brobecker To: Phil Prentice Cc: gdb@sources.redhat.com Subject: Re: GDB & VxWorks 5.4 Message-ID: <20030612181509.GU947@gnat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-SW-Source: 2003-06/txt/msg00214.txt.bz2 > The target GDB server (tRDBtask) software for VxWorks 5.2 has been replaced > in VxWorks 5.4 with WDB. We would like to continue to use vxgdb to interface > with VxWorks 5.4? Has anybody got any suggestions? Not sure I understand correctly what you are talking about, since I've never played with VxWorks 5.2. However, with 5.4, you can/should have a target server that runs on the host. This target server should handle all the WDB communication between you and the target. As for you, you should be talking to him using the WTX protocol. There is a C API that you can use for that. -- Joel