Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: GDB's low hanging backlog
Date: Tue, 24 Aug 2004 19:45:00 -0000	[thread overview]
Message-ID: <412B9A7D.1080304@gnu.org> (raw)
In-Reply-To: <4116A287.7000108@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 6 bytes --]

Ping.

[-- Attachment #2: Attached Message --]
[-- Type: message/rfc822, Size: 4383 bytes --]

From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: GDB's low hanging backlog
Date: Sun, 08 Aug 2004 18:00:39 -0400
Message-ID: <4116A287.7000108@gnu.org>

Hello,

GDB's got a number of those almost complete changes that never seem to 
go away.  While these are things that don't attract the glamor of key 
new features, they are equally important as by closing these tasks off 
we ensure that GDB is moving forward in a steady and healthy way.

I'd like to see a few of these tasks finally closed, and with a bit of 
focused effort we can do it.

Here's what's I see as relatively low hanging fruit:


-- builtin_type_* as a function

The builtin_types have finally been moved to the architecture vector. 
The task of going through GDB and switching to the per-architecture 
method remains.

The tricky area is the language code.


-- shlibs in architecture vector

I guess it needs a final shove?  Anything else holding it up?


-- tm*.h removal a.k.a. true multi-arch

See above for road blocks.  I _think_ that's it!   GDB being able to 
support both native and remote debugging for mixed architectures becomes 
a reality.


-- xm*.h removal
Thanks to Joel, AIX is [almost] fixed.  That just leaves the DOS file 
formats.


-- i18n

We need to get GDB's strings marked up.


Also lurking in the wings are:


-- CXX compile

GCC's ahead of us here and already started the process.  It should be 
possible to build GDB using the C++ compiler (which is very different to 
GDB being written in C++ :-).


-- nm*.h removal

Probably not so easy.  The contents should be either in the architecture 
or target vector.


What have I forgotten?

Who would like to help?

Andrew




  parent reply	other threads:[~2004-08-24 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 13:58 Andrew Cagney
2004-08-09 16:28 ` Michael Chastain
2004-08-24 19:45 ` Andrew Cagney [this message]
2004-08-24 22:38   ` Baurjan Ismagulov
2004-08-27 16:04     ` Andrew Cagney
2004-08-25  8:22   ` Orjan Friberg
2004-08-27 16:16     ` Andrew Cagney

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=412B9A7D.1080304@gnu.org \
    --to=cagney@gnu.org \
    --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