From: Brendan Simon <brendan@dgs.monash.edu.au>
To: gdb <gdb@cygnus.com>
Subject: GDB: one version for all targets
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <36CA2891.A1C43ED2@dgs.monash.edu.au> (raw)
In-Reply-To: <199902162128.NAA25807@andros.cygnus.com>
From some of the discussions on this list, I have interpretted that GDB may
be moving to one version that can dynmically detect the CPU target and ABI
type. A manual setting for these is provided as a fallback if autodetection
fails.
Does this mean there would only be one GDB that would cater for all targets.
eg. i386, powerpc, m68k, etc ?
This sounds like a fantastic idea and I look forward to such a versatile
debugger.
Does anyone know when this is likely to be available ?
I assume the correct simulator would be called based on the above settings.
To reduce diskspace, would it be possible to have the supported targets and
ABI types as some kind of shared library or plug in module ?
Brendan Simon.
From devnull@gnu.org Thu Apr 01 00:00:00 1999
From: "Joel N. Weber II" <devnull@gnu.org>
To: gnu-prog@gnu.org
Subject: ftp.gnu.org redisorganization
Date: Thu, 01 Apr 1999 00:00:00 -0000
Message-id: <199901080426.XAA08145@melange.gnu.org>
X-SW-Source: 1999-q1/msg00015.html
Content-length: 1058
I have redisorganized ftp.gnu.org so that there is now a directory for
every package (although at the moment, the emacs lisp manual, the
emacs lisp intro, leim, and elib all exist in the emacs directory; we
may rearange that). For example, there exists a directory at
ftp://ftp.gnu.org/gnu/emacs which contains various versions of emacs.
Someone had suggested that we should also make
ftp://ftp.gnu.org/gnu/emacs/emacs.tar.gz a symlink to the .tar.gz of
the current version. We rejected this possibility; if we do this,
people will end up with .tar.gz files on their local disks that lack
the version number.
If people notice problems with how the redisorganization was done,
please let me know.
We are now willing to make links to these directories from webpages
under http://www.gnu.org/software ; so please feel free to update your
web pages (or create web pages for your packages, if you haven't
already!). If we haven't given you more specific instruction on what
to do to submit new or changed webpages, please mail them to
webmasters@gnu.org.
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199812041858.KAA25185.cygnus.gdb@jtc.redbacknetworks.com>
1998-12-10 19:27 ` breakpoint extension for remote protocol Andrew Cagney
1998-12-10 21:46 ` Stu Grossman
1998-12-11 11:59 ` J.T. Conklin
1998-12-11 14:30 ` J.T. Conklin
1998-12-11 11:24 ` J.T. Conklin
[not found] ` <13936.45476.191551.329690.cygnus.gdb@babylon-5.cygnus.com>
1999-04-01 0:00 ` Andrew Cagney
1999-04-01 0:00 ` J.T. Conklin
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` J.T. Conklin
1999-04-01 0:00 ` Brendan Simon [this message]
1999-04-01 0:00 ` GDB: one version for all targets Stan Shebs
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=36CA2891.A1C43ED2@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=gdb@cygnus.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