From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24727 invoked by alias); 18 Feb 2004 14:52:17 -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 24710 invoked from network); 18 Feb 2004 14:52:15 -0000 Received: from unknown (HELO cam-admin0.cambridge.arm.com) (193.131.176.58) by sources.redhat.com with SMTP; 18 Feb 2004 14:52:15 -0000 Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.12.10/8.12.10) with ESMTP id i1IEq523029193; Wed, 18 Feb 2004 14:52:05 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id i1IEq5526448; Wed, 18 Feb 2004 14:52:05 GMT Message-Id: <200402181452.i1IEq5526448@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: "Vineet Sharma, Noida" cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Re: Add systemc simulator with gdb In-reply-to: Your message of "Wed, 18 Feb 2004 19:53:38 +0530." <1B3885BC15C7024C845AAC78314766C5036B65F3@exch-01.noida.hcltech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Feb 2004 14:52:00 -0000 From: Richard Earnshaw X-SW-Source: 2004-02/txt/msg00227.txt.bz2 > > Hi All, > > Is there any examples who have sucessfully integrated there > simulators in c++ or systemc with gdb? I'm guessing that most people on this list won't even know what systemc is [*], let alone really understand what question you are asking. > What are the issues faced in that approach? gdb can be used for debugging c++ and other normal programming languages. It isn't really an HDL debugger. > > I found the problem of conflicting types of bfd in bfd.h and > remote-sim.h(:67). Any idea how to overcome it? > > ../../include/gdb/remote-sim.h:67: conflicting types for `struct bfd' > /usr/include/bfd.h:78: previous declaration as `typedef struct _bfd bfd' > ../../include/gdb/remote-sim.h:108: using typedef-name `bfd' after `struct' > ../../include/gdb/remote-sim.h:145: using typedef-name `bfd' after `struct' > ../../include/gdb/remote-sim.h:165: using typedef-name `bfd' after `struct' > I think its bcoz of the difference in c++/g++ and gcc handling of > forward declaration? > GDB is written in C, and needs to be compiled with a C compiler. It's not C++, and I guess that if you try and compile it with G++ you'll get error messages much like the one above. R. [*] For the uninitiated, SystemC started life as a simulation class library for C++ which enables you to use C++ in much the same way as you would any other HDL (Hardware description language). However, by restricting your description a suitable subset of C++ you can then accelerate it significantly with special simulators and even run hardware synthesis tools on it. The real power comes from the fact that your test benches can be written in abstract C++ and can then interact with your hardware description directly.