Can't get GDB to connect to target

Can't get GDB to connect to target

[Gerwyn Davies]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

I cannot get GDB to connect  to my remote 
taget. 
 
I get a message 'Remote debugging using com1', 
and thats it,  GDB has locked up.
 
Is there any debug information that I can get 
out from GDB?
 
Gerwyn

Re: Can't get GDB to connect to target

[Eli Zaretskii]

> From: "Gerwyn Davies" <gerwynd@tommoll.freeserve.co.uk>
> Date: Sun, 25 Jun 2000 22:18:09 +0100
> 
> I cannot get GDB to connect  to my remote taget.
> 
> I get a message 'Remote debugging using com1', and thats it,  GDB has
> locked up.

You don't say what version of GDB and on what platform did you try
this.  `com1' implies the MS-DOS (a.k.a. DJGPP) port of GDB.  Is that
true?
From scottb@netwinder.org Mon Jun 26 11:38:00 2000
From: Scott Bambrough <scottb@netwinder.org>
To: GDB Mailing List <gdb@sourceware.cygnus.com>
Cc: binutils mailing list <binutils@sourceware.cygnus.com>
Subject: DEJAGNU will not build...
Date: Mon, 26 Jun 2000 11:38:00 -0000
Message-id: <3957A1D3.3E81F34@netwinder.org>
X-SW-Source: 2000-06/msg00183.html
Content-length: 542

I am unable to get dejagnu to build.  I have checked out the dejagnu sources,
and downloaded the latest tarball from sourceware.  It refuses to build anything
with a dependency on ./include/libiberty.h.  This file (actually the whole
directory) is not present when the module is checked out.  Should the directory
be added to the module, the configury changed to setup INCDIR correctly, or am I
just doing something dumb?

Scott

-- 
Scott Bambrough - Software Engineer
REBEL.COM    http://www.rebel.com
NetWinder    http://www.netwinder.org
From gerwynd@tommoll.freeserve.co.uk Mon Jun 26 14:18:00 2000
From: "Gerwyn Davies" <gerwynd@tommoll.freeserve.co.uk>
To: "GDB" <gdb@sourceware.cygnus.com>
Subject: Re: Can't get GDB to connect to target
Date: Mon, 26 Jun 2000 14:18:00 -0000
Message-id: <005c01bfdfb4$6bb38e20$541a893e@gtd-s-machine>
X-SW-Source: 2000-06/msg00184.html
Content-length: 1440

I'm running GDB from a BASH shell on a Windows 98 platform. The version and
configuration of GDB is:-

>GNU gdb 4.17-gnupro-98r2
>This GDB was configured as
"--host=i586-pc-cygwin32 --target=mips-tx39-elf".

This version was supplied to me along with the demo board that I'm trying to
connect to. I assume I was given a good working setup. I've also compiled a
version 5 build of GDB which showed a similar problem.

I'm also reasonably sure my monitor is all OK. If I connect to it using  a
terminal emulator, I can stimulate the transmission of GBD protocol packets.

There must be some diagnostics available from GDB somewhere.

I've never used these GNU tools before, so I expect to encounter some very
fundamental problems most likey caused by my errors.

Many thanks.

-----Original Message-----
From: Eli Zaretskii <eliz@delorie.com>
To: gerwynd@tommoll.freeserve.co.uk <gerwynd@tommoll.freeserve.co.uk>
Cc: gdb@sourceware.cygnus.com <gdb@sourceware.cygnus.com>
Date: 26 June 2000 06:38
Subject: Re: Can't get GDB to connect to target


>> From: "Gerwyn Davies" <gerwynd@tommoll.freeserve.co.uk>
>> Date: Sun, 25 Jun 2000 22:18:09 +0100
>>
>> I cannot get GDB to connect  to my remote taget.
>>
>> I get a message 'Remote debugging using com1', and thats it,  GDB has
>> locked up.
>
>You don't say what version of GDB and on what platform did you try
>this.  `com1' implies the MS-DOS (a.k.a. DJGPP) port of GDB.  Is that
>true?
>

Re: Can't get GDB to connect to target

[Nicolas.Thery]

"Gerwyn Davies" <gerwynd@tommoll.freeserve.co.uk> wrote:

>
> I'm running GDB from a BASH shell on a Windows 98 platform. The version
and
> configuration of GDB is:-
>
> >GNU gdb 4.17-gnupro-98r2
> >This GDB was configured as
> "--host=i586-pc-cygwin32 --target=mips-tx39-elf".
>
> This version was supplied to me along with the demo board that I'm trying
to
> connect to. I assume I was given a good working setup. I've also compiled
a
> version 5 build of GDB which showed a similar problem.
>
> I'm also reasonably sure my monitor is all OK. If I connect to it using
a
> terminal emulator, I can stimulate the transmission of GBD protocol
packets.
>
> There must be some diagnostics available from GDB somewhere.

Enter "set remotedebug 1" before "target remote com1".

This will dump to the screen sent and received packets.