Hi Steve/Daniel,

Thanks very much for your help ! I've now got a few days "homework" to
try out :-)

Regards, Stuart


Daniel Jacobowitz wrote:

On Tue, Sep 17, 2002 at 12:24:14PM -0500, Steven J. Hill wrote:

quoted

Stuart Hughes wrote:

quoted

Does anyone know whether there is some special setup needed on
gdb/gdbserver to use the multi-threaded gdbserver ??

Wow, there are so many things to tell you...where to start...

Steve, have you started memorizing my responses again? :)

quoted

quoted

My environment is as follows:

CPU:         NEC VR5432
kernel:      linux-2.4.18 + patches
glibc:               2.2.3 + patches
gdb:         5.2/3 from CVS

Has to be the gdb-5.3 branch...go look at http://sources.redhat.com/gdb

quoted

gcc:         3.1
binutils:    Version 2.11.90.0.25

Don't use H.J. Lu's binutils, use the released one. Use gcc-3.2 and
binutils-2.13 as they have fixes for the MIPS debugging symbols with
regards to DWARF.

quoted

cross-gdb configured using:

configure --prefix=/usr --target=mipsel-linux --disable-sim
--disable-tcl --enable-threads --enable-shared

Use '--target=mips-linux' and you'll be better off. Don't worry, it
will support both endians.

Except for this one - where'd that come from?  It should make no
functional difference either way, at least assuming you always give GDB
a binary.

quoted

quoted

gdbserver configured using:

configure --prefix=/usr --host=mipsel-linux --target=mipsel-linux
--enable-threads --enable-shared

I would also try 'CC=mipsel-linux-gcc configure <...>'.

Definitely.

--
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer