Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [www/RFA] Remove references to libgdb in GDB's web pages
Date: Fri, 27 Mar 2009 15:55:00 -0000	[thread overview]
Message-ID: <20090327155041.GR9472@adacore.com> (raw)
In-Reply-To: <200903271412.49317.pedro@codesourcery.com>

> I'm a bit unconfortable in making a piece of history just disappear.
> 
> Can't we instead remove "current" from the link, and say somewhere that
> this is not the path that GDB is now following?  Perhaps a short sensence
> below the link?

I can certainly do that. I'm not that uncomfortable because I think
it was a bad idea - bad idea for us due to the overhead of providing
a stable API, and also a bad idea (IMO) for the users, as it is much
more flexible to have the debugging module as a separate process
(if the process SEGVs, you don't die with it, of if there is a bug
in GDB you can switch to a newer version of GDB without changing
version of your tool, etc).

But perhaps you're right. I did certainly think at first that a libgdb
would be great. So it might be interesting to have a note on the website
explaining that this is no longer a current project. At least people
won't think that the idea is new and exciting.

Anway, will send a patch along what you propose ASAP. We can choose
whichever we prefer.

-- 
Joel


  reply	other threads:[~2009-03-27 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 22:23 Joel Brobecker
2009-03-27 14:39 ` Pedro Alves
2009-03-27 15:55   ` Joel Brobecker [this message]
2009-03-30 17:02   ` Joel Brobecker
2009-03-31 13:46     ` Pedro Alves

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=20090327155041.GR9472@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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