From: "Igor Trevisan" <igor.trevisan@bluewind.it>
To: Keith Seitz <keiths@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gdb/Insight and WinNT problem
Date: Wed, 27 Feb 2002 00:51:00 -0000 [thread overview]
Message-ID: <3C7CAC1D.14700.199B71@localhost> (raw)
In-Reply-To: <Pine.GSO.4.33.0202260929400.20025-100000@makita.cygnus.com>
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
>
>
>
prev parent reply other threads:[~2002-02-27 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 2:13 Igor Trevisan
[not found] ` <Pine.GSO.4.33.0202260859090.20025-100000@makita.cygnus.com>
2002-02-26 9:11 ` Igor Trevisan
2002-02-26 9:31 ` Keith Seitz
2002-02-27 0:51 ` Igor Trevisan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C7CAC1D.14700.199B71@localhost \
--to=igor.trevisan@bluewind.it \
--cc=gdb@sources.redhat.com \
--cc=keiths@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox