Gdb, threads, DDD and remote debugging.

Gdb, threads, DDD and remote debugging.

[Rok Papez]

Hello!

Could someon please RTFM me to some documentation that explains how to set-up
gdb for remote debugging, either thru ethernet or serial cable. If used for
remote debugging, are there any catches with multiple threads? 
Does DDD support remote debugging?

Platform: x86, Linux, RH 6.0 with gdb-4.17.0.14-1


-- 
best regards,
Rok Papez.
From eliz@gnu.org Tue Nov 23 05:03:00 1999
From: Eli Zaretskii <eliz@gnu.org>
To: jimb@cygnus.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: none
Date: Tue, 23 Nov 1999 05:03:00 -0000
Message-id: <199911231303.IAA01523@mescaline.gnu.org>
References: <199911090706.CAA13120@zwingli.cygnus.com> <199911102246.RAA01846@mescaline.gnu.org> <npr9hi321d.fsf@zwingli.cygnus.com>
X-SW-Source: 1999-q4/msg00311.html
Content-length: 1181

> So, does the compiler use separate numbers in the debug for MMX
> registers and FP stack registers, or the same numbers?
> 
> If the compiler uses separate register numbers, then we have the
> problems discussed before: as far as I can tell, GDB simply isn't set
> up to cope with the idea that certain bits might be part of two
> registers.
> 
> If the compiler uses the same register numbers, how can the
> architecture-specific code tell whether GDB is accessing MM0 (which
> lives in R0) or ST(0) (which lives in R(TOS))?

The architecture-specific code knows about TOS, right?  It's part of
the status word, so it's available to GDB.  Since TOS is handled the
same by all x86 platforms, we could use the value of TOS to define two
x86-specific functions to map between ST(i) and the corresponding MMj
register and back.

Given these mapping functions, the code which implements the MMX view
of the FP registers could allow both reading and writing MMX registers
by accessing the corresponding ST(i) registers, each time using the
current value of TOS.

Am I missing something obvious?  If so, perhaps I don't understand how
the register views are (or would be) implemented.
From mainguen@gabin.frcl.bull.fr Tue Nov 23 08:20:00 1999
From: Bernard Mainguenaud <mainguen@gabin.frcl.bull.fr>
To: gdb@sourceware.cygnus.com
Subject: Gdb target for kdb
Date: Tue, 23 Nov 1999 08:20:00 -0000
Message-id: <199911231620.RAA29254@gabin.frcl.bull.fr>
X-SW-Source: 1999-q4/msg00312.html
Content-length: 306

Hello,

We intend to use gdb to debug a running Linux kernel connected
to another Linux box via an asynchronous line. For this purpose,
we are considering developping a new gdb target that interfaces
with kdb. Has anyone ever tried to develop such a kdb target
before ?

Best regards,
Bernard Mainguenaud.
From chitti@wipinfo.soft.net Tue Nov 23 08:40:00 1999
From: Chitti Raju <chitti@wipinfo.soft.net>
To: ebachalo@cygnus.com (Eric Bachalo)
Cc: chitti@wipinfo.soft.net, gdb@sourceware.cygnus.com
Subject: Re: 64bit GDB
Date: Tue, 23 Nov 1999 08:40:00 -0000
Message-id: <199911231641.WAA18797@gem.wipinfo.soft.net>
References: <3839B0D5.FB1D4AC3@cygnus.com>
X-SW-Source: 1999-q4/msg00313.html
Content-length: 1712

I would like to be a full fledged volunteer to the GDB 64-bit(sparc/sol2.7)
activity. I mean to say i would like to closely work with the cygnus 
developers who are working on this 64-bit activity. 
Will cygnus allow this type of voluntary work.
For the first one month i can work 4hrs/day, and the from the next month on 
8hrs/day. I'm confident that i can pick up to the mark in the first one month. 
I have a good amount of experience in debuggers also. right now i'm working on 
a parallel debugger project. in that we are using the GDB as a client, 
which mainly handles debugging symbol information. I'm also working on a 
patch which enables the gdb to debug an application, that is compiled using
sunwspro compiler with out -xs flag. I will submit/open up a discussion 
on this in a few days.

Thanks,
Chitti
email:chitti@wipinfo.soft.net
> 
> Chitti,
> 
> http://www.cygnus.com/news/gnusolaris012199.html
> 
> As you can see from our press release, we do have a contract to support 64-bit
> Solaris.  This work is quite extensive.  The 64-bit Solaris support should be
> showing up in the GDB snapshots in early to late summer, 2000.
> 
> 
> Best Regards,
> 
> Eric Bachalo
> 
> 
> 
> Chitti Raju wrote:
> > 
> > This is regarding the 64-bit version of GDB.
> > I have some questions on this subject:
> > 1. Is there any work in progress to make GDB 64-bit
> > 2. GDB depends on libraries like libbfd, libreadline, libopcodes and libiberty
> >    Are these libraries 64-bit compliant
> > 3. has anyone worked on this earlier and willing to share their work.
> > Even if you know some issues related to 64-bit GDB, pls feel free
> > to mail me at chitti@wipinfo.soft.net
> > 
> > Thanks,
> > Chitti.
>