From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14512 invoked by alias); 19 Sep 2002 02:05:35 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 14504 invoked from network); 19 Sep 2002 02:05:33 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 19 Sep 2002 02:05:33 -0000 Received: from tooth.toronto.redhat.com (tooth.toronto.redhat.com [172.16.14.29]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 6C8F8B8831; Wed, 18 Sep 2002 22:05:33 -0400 (EDT) Received: (from fche@localhost) by tooth.toronto.redhat.com (8.11.6/8.11.6) id g8J25Xu25627; Wed, 18 Sep 2002 22:05:33 -0400 Date: Wed, 18 Sep 2002 19:05:00 -0000 From: "Frank Ch. Eigler" To: T Satish Kumar Cc: Keith Seitz , sid@sources.redhat.com Subject: Re: Fw: [ECOS] how to build an eCos library for ARM7tdmi simulator Message-ID: <20020918220533.B24977@redhat.com> References: <001501c25ff2$7cc84820$19b6b486@sltisatish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <001501c25ff2$7cc84820$19b6b486@sltisatish>; from satish@td.idc.lsi.sanyo.co.jp on Thu, Sep 19, 2002 at 08:37:39AM -0700 X-SW-Source: 2002-q3/txt/msg00068.txt.bz2 Hi - On Thu, Sep 19, 2002 at 08:37:39AM -0700, T Satish Kumar wrote: > well, No, even after running > 1. arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL & > 2.arm-elf-gdb -nw twothreads.x > 3. target remote localhost:2000 > i get a message displaying: > > localhost:2000 Attempt to connect timed out with out establishing a > connection. > > well, incase i run arm-elf-sid with --tksm option , i get a stackdump (i.e > sid.exe.stackdump) Neither of these two failures sound familiar. Perhaps you have a misbuilt or misinstalled simulator, or some other unique problem. For the first case, try adding "-v" to the arm-elf-sid command line: it will produce lots of tracing output, the tail end of which should give some hint about what's going wrong. Try a TCP port number other than 2000. You can try catching sid's crash under a debugger, if you first "arm-elf-sid --no-run [other-options]", then run sid directly under the debugger: "gdb -args sid sid.conf"/"run" or somesuch. > i m not able to proceed further after this in either cases.. > someone plz help me at the earliest.. For what it's worth, Red Hat offers support contracts on its software, which entitle customers to more in-depth help than you might have reason to expect here. - FChE