From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6435 invoked by alias); 27 Feb 2002 08:51:53 -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 6331 invoked from network); 27 Feb 2002 08:51:51 -0000 Received: from unknown (HELO fep02-svc.flexmail.it) (212.131.248.101) by sources.redhat.com with SMTP; 27 Feb 2002 08:51:51 -0000 Received: from igortr ([80.105.50.61]) by fep02-svc.flexmail.it (InterMail vM.5.01.03.08 201-253-122-118-108-20010628) with ESMTP id <20020227085152.QPST17441.fep02-svc.flexmail.it@igortr>; Wed, 27 Feb 2002 09:51:52 +0100 From: "Igor Trevisan" To: Keith Seitz Date: Wed, 27 Feb 2002 00:51:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: gdb/Insight and WinNT problem CC: Message-ID: <3C7CAC1D.14700.199B71@localhost> Priority: normal References: <3C7BCFA1.22512.208A3CC@localhost> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) X-SW-Source: 2002-02/txt/msg00318.txt.bz2 Hi Keith, I send you a list of the steps that produces, in my working environment, the crash I told you: First a note: my PC is connected through ethernet to an EPI Jeeni ARM emulator through which I debug code on the target (derived from a EDB7209 Cirrus Logic Board). - I launch gdb (Insight GUI) from a cygwin (1.3.9-1 release), from the directory where I have the executable file; - I open the console window; - using the console I give the command: file executable.elf - then I select "connect to target" from the "run" menu in the debugger window. Following are my settings: set breakpoint at "main" set breakpoint at "exit" set breakpoint at 0x00000040 (reset_vector) remote/TCP to IP of the Jeeni, port 1000 (as I find written on the "run/connect" window); other selections are: attach to the target, download program and continue from last stop. Then I press enter and the debugger stays locked for a short time; then the following error message appears: "192.168.0.12:1000 Attemp to connect timed out without establishing a connection. GDB cannot connect to the target board using 192.168.. etc. Verify that the board is securely connected (and it is!!) and, if necessary, modify the port setting with the debugger preferences" So I press OK on the error message window and my WinNT 4.0 PC crashes and restart!! Some notes: If I connect to the target giving commands from console I can successfully connect and load the .elf file. There are other cases in which I had a crash, but, you know, it's not so funny spend a day looking to rebuild them!! ;-) I hope this can help you to discover something... Thanks for your interest, Igor. On 26 Feb 2002, at 9:31, Keith Seitz wrote: > On Tue, 26 Feb 2002, Igor Trevisan wrote: > > > First of all thanks in every case for your answer! > > Then... > > I'm using gdb/Insight 5.1 configured as "--host=i686-pc-cygwin" > > "--target=arm-elf", with cygwin-1.3.9-1. > > Hmm. These are known problems with CVS head, not with 5.1. > > > And... a new question: will I have similar problems > > passing to Win2000? If it is known... > > NT and 2000 should be just about interchangable. I use Win2000 almost > exclusively now. (Occasionally booting win98 to watch DVDs while I > work!) > > Having said all that, can you give me a procedure to reproduce your > problem? > > Keith > > >