From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21610 invoked by alias); 20 Apr 2004 08:12:45 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 21602 invoked from network); 20 Apr 2004 08:12:43 -0000 Received: from unknown (HELO indonesia.kscanners.no) (193.214.130.21) by sources.redhat.com with SMTP; 20 Apr 2004 08:12:43 -0000 Received: from localhost ([127.0.0.1] helo=procaptura.com) by indonesia.kscanners.no with esmtp (Exim 4.30) id 1BFqMz-0000wm-R0 for insight@sources.redhat.com; Tue, 20 Apr 2004 10:12:41 +0200 Message-ID: <4084DB79.20105@procaptura.com> Date: Tue, 20 Apr 2004 08:12:00 -0000 From: Toralf Lund User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) MIME-Version: 1.0 To: insight@sources.redhat.com Subject: Re: Insight + ARM-9 + BDI2000: Hang on exec References: <4083CC5E.6060502@procaptura.com> <1082393564.2007.3.camel@lindt.uglyboxes.com> In-Reply-To: <1082393564.2007.3.camel@lindt.uglyboxes.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-q2/txt/msg00010.txt.bz2 Keith Seitz wrote: >On Mon, 2004-04-19 at 05:55, Toralf Lund wrote: > > >>I'm using insight built for ARM along with the BDI2000 (BDIGDB) debug >>"POD" to debug a custom interface card based on the MC9328 (ARM-9 core) >>processor. >> >> > >First things first: does it run under console gdb? ("insight -nw" or >"gdb")? > > Yes, it runs under gdb (I thought I said that). Well, actually, the code crashes after a while, but I can at least set some breakpoints, have it stop there, step the code etc. One problem, though: I sometimes get :2001: Connection refused. for no apparent reason, when issuing a "target" command. If I try the same operation again, it usually works fine. Also, even insight was OK for a while, then something (related to the application - insight hasn't changed) happened that made it stop working - and I can't figure out what it is ;-/ >There are numerous reasons for failures of this kind. Typically, it is >an error in the target code in gdb. Testing command-line gdb is the >first step to ascertaining where the problem lies. > >Also, could you send a more complete, step-by-step description of what >you did? From your post, I'm not entirely sure how you got it to hang. > > I got it to hang simply by starting the code (which is why I didn't think it necessary to give any steps), i.e. 1. arm-coff-insight 2. Run->Download 3. Run->Run After I wrote the original message, I discovered that there are other ways, like 1. arm-coff-insight 2. Run->Download 3. File->Exit (But Exit does work if I do File->Disconnect first.) Furthermore, 1. arm-coff-insight 2. Run->Download 3. Control->Next Asm Inst (since execution start with start() written in assembler. 4. Other "step" commands... Actually works, but if I try e.g. View->Registers, I get another hang, but of a slightly different type; this time I get a "stop" icon and "busy" cursor, but I'm not really allowed to stop the process. >Keith > > >