This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: threads/1655: Undocumented feature: how to build gdb for threads
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 24 May 2004 18:48:01 -0000
- Subject: Re: threads/1655: Undocumented feature: how to build gdb for threads
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR threads/1655; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: Robert Trask <rtrask@earthlink.net>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: threads/1655: Undocumented feature: how to build gdb for threads
Date: Mon, 24 May 2004 14:46:36 -0400
On Mon, May 24, 2004 at 10:43:47AM -0800, Robert Trask wrote:
> We are (were) building a cross gdb targeted at remote platforms as follows:
>
> host = x86 linux
> target = mips-linux
>
> config args as follows (from config.status)
> ../configure --target=mips-linux --host=i686-pc-linux --enable-threads
>
> If you do not supply the --enable-threads argument the gdb will still work -- but not for targets using threads. More acurately, gdb will work but won't be able to handle thread inquiries, won't have a valid stack frame, etc.
>
> The sources are unmodified gdb release 6.1, straight from the gdb website (uncompress & untar the tarball etc).
> The same argument (--enable-threads) is required for building the gdbserver component that runs on the target.
Sorry, but --enable-threads doesn't do anything. You'll have to
investigate why it makes a difference for you; GDB does not even check
the value of that option.
--
Daniel Jacobowitz