From: Brian Dessent <brian@dessent.net>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: insight@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [3/3] Remove deprecated_register_gdbarch_swap infrastructure
Date: Wed, 27 Jun 2007 06:52:00 -0000 [thread overview]
Message-ID: <4681B910.30B50240@dessent.net> (raw)
In-Reply-To: <200706270013.l5R0DDii030369@d12av02.megacenter.de.ibm.com>
Ulrich Weigand wrote:
> I've actually never looked at Insight before. Where's that code
> located?
It's in the same repository as gdb, except using the module name
'insight' instead of 'gdb'.
From looking at the modules file it looks like you could get an insight
checkout by starting with a gdb checkout and then adding the gdb/gdbtk
and gdb/testsuite/gdb.gdbtk directories, plus the tcl/tk stuff:
naked-gdb-guifull -a src/gdb
naked-gdb -a !src/gdb/gdbtk !src/gdb/testsuite/gdb.gdbtk src/gdb
gdb-support -a naked-texinfo naked-bfd naked-opcodes \
naked-readline naked-libiberty naked-include \
naked-sim naked-cpu src/djunpack.bat naked-intl \
src-support
# Module reflecting active development.
gdb -a naked-gdb gdb-support
gdb+dejagnu -a gdb naked-dejagnu naked-expect naked-tcl
gdb+binutils -a gdb naked-binutils naked-gas naked-gprof naked-ld
binutils+gdb -a gdb+binutils
gdb+dejagnu+binutils -a gdb+dejagnu naked-binutils naked-gas naked-gprof
naked-ld
gdb+binutils+dejagnu -a gdb+dejagnu+binutils
binutils+gdb+dejagnu -a gdb+dejagnu+binutils
insight -a naked-gdb-guifull gdb-support \
naked-tcl naked-tk naked-itcl naked-tix naked-libgui
insight+dejagnu -a insight naked-dejagnu naked-expect
Brian
prev parent reply other threads:[~2007-06-27 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 23:23 Ulrich Weigand
2007-06-12 15:35 ` Daniel Jacobowitz
2007-06-22 12:54 ` Ulrich Weigand
2007-06-26 18:30 ` Brian Dessent
2007-06-27 1:10 ` Ulrich Weigand
2007-06-27 6:52 ` Brian Dessent [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=4681B910.30B50240@dessent.net \
--to=brian@dessent.net \
--cc=gdb-patches@sourceware.org \
--cc=insight@sourceware.org \
--cc=uweigand@de.ibm.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