Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Dan Kegel <dank@kegel.com>
Cc: Christoph Plattner <christoph.plattner@gmx.at>,
	Andrew Cagney <ac131313@cygnus.com>,
	gdb@sources.redhat.com
Subject: Re: `gdbserver' in cross compiled builds
Date: Sun, 24 Feb 2002 10:25:00 -0000	[thread overview]
Message-ID: <20020224132454.A11571@nevyn.them.org> (raw)
In-Reply-To: <3C79310D.C6C83AF2@kegel.com>

On Sun, Feb 24, 2002 at 10:29:33AM -0800, Dan Kegel wrote:
> Daniel Jacobowitz wrote:
> > > ... Why does the gdbserver directory work so bad ?
> > 
> > Use current CVS instead.  I've spent months fixing this.
> > 
> > In fact, if you get current CVS, you can:
> > mkdir obj
> > cd obj
> > ../src/gdb/gdbserver/configure
> > make
> > 
> > And build only the server.
> 
> Oooh, thanks.  I'll have to try that.
> 
> What's the word on gdbserver and multithreaded programs?
> Were those patches from Michal Korbal on track, or is
> the right solution going forward something different?

A little bit different.  I'm working on it now.

His patches were unfortunately based on a GDB module that's been
obsoleted; someone interested could probably hack them into a usable
state, but not into a good one.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-02-24 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C5B3201.2F2FB670@gmx.at>
2002-02-23  9:31 ` Andrew Cagney
     [not found]   ` <3C780221.CF27FBDA@gmx.at>
2002-02-23 13:26     ` Andrew Cagney
2002-02-24  3:26       ` Christoph Plattner
2002-02-24  8:37         ` Daniel Jacobowitz
2002-02-24 10:21           ` Dan Kegel
2002-02-24 10:25             ` Daniel Jacobowitz [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=20020224132454.A11571@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=christoph.plattner@gmx.at \
    --cc=dank@kegel.com \
    --cc=gdb@sources.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