gdb/Insight and WinNT problem

gdb/Insight and WinNT problem

[Igor Trevisan]

Hi all!

I'm using gdb with Insight GUI with cygwin under WInNT 4.0
and I'm having some problems.
In particular there are some situatuion that make WinNT crash!!
This happens if I try to use the option
"Target settings..." from the "file" or 
"Connect to target" from the "run" menu.
This particulary happens if I select that option, for example
while I'm using gdb sinulator with Insight.
Is this a already known problem? If so, is there
any explaination/solution for it?
Just to give you a more complete overview...
I'm using gdb/Insight 5.1 configured as "--host=i686-pc-cygwin" 
"--target=arm-elf", with
cygwin-1.3.9-1.
Thanks for every kind of help...
	Igor.

-----------------------------------------------------------------
BlueWind          Embedded Systems Design
Via Steffani 7/B
31033 Castelfranco Veneto (TV)
-----------------------------------------------------------------
Office  +39 0 423 723431
Fax     +39 0 423 744738
Mobile  +39 335 7298820

mailto:igor.trevisan@bluewind.it
http://www.bluewind.it
----------------------------------------------

Re: gdb/Insight and WinNT problem

[Igor Trevisan]

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.
And... a new question: will I have similar problems
passing to Win2000? If it is known...
Thanks again...
Nice greetings,
	Igor.

On 26 Feb 2002, at 9:00, Keith Seitz wrote:

> [moved to insight mailing list]
> 
> On Tue, 26 Feb 2002, Igor Trevisan wrote:
> 
> > I'm using gdb with Insight GUI with cygwin under WInNT 4.0
> > and I'm having some problems.
> > In particular there are some situatuion that make WinNT crash!! This
> > happens if I try to use the option "Target settings..." from the
> > "file" or "Connect to target" from the "run" menu.
> 
> What version of Insight are you using? CVS head? If so, this is a
> known problem. There are several pending patches to fix this, but it's
> slow going...
> 
> Keith
> 
> 
> 

Re: gdb/Insight and WinNT problem

[Keith Seitz]

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

Re: gdb/Insight and WinNT problem

[Igor Trevisan]

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
> 
> 
>