From: piet delaney <piet@freebsd.piet.net>
To: Jim Wilson <wilson@redhat.com>
Cc: piet delaney <piet@freebsd.piet.net>,
Rags <rags@freebsd.piet.net>,
linux-ia64@linuxia64.org, gdb@sources.redhat.com
Subject: Re: [Linux-ia64] debuggers - ia64 gdb stubs?
Date: Thu, 28 Mar 2002 22:24:00 -0000 [thread overview]
Message-ID: <20020329142309.A8255@www.piet.net> (raw)
In-Reply-To: <20020329064011.A6198@www.piet.net>; from piet@freebsd.piet.net on Fri, Mar 29, 2002 at 06:40:11AM -0800
On Thu, Mar 28, 2002 at 07:00:33PM -0800, Jim Wilson wrote:
> >Besides gdb and ddd what other types of debuggers are available for IA64?
>
> ddd is a graphical front end for debugggers, it isn't a debugger itself.
> If you are using ddd, then you are likely still using gdb underneath as
> the real debugger. If you want a list of gdb front ends... there is an emacs
> gdb mode which is the front end that I use. There is gdbtk which is a
> graphical X windows front end that uses tcl/tk. There is also a curses based
> text window front end called tui, originally from HP, but I've never used that
> one so I don't know anything about it.
>
> As for other debuggers besides gdb, I know that Intel has one which comes
> with the Intel compilers. It implements a gdb-like command set. This debugger
> is called LDB, the Linux debugger.
>
> There are of course other debuggers for other operating systems, but they
> aren't useful on ia64-linux systems.
I was currious if anyone else interested-in/working-on a gdb stub for ia64?
I've been modifying the i386 version of a kdb to gdb stub, skdb, to work
on the ia64, and was thinking of playing around this weekend a bit and
sorting out register assignment problems. I just thought I'd see if anyone
else was interested-in or working-on this or a direct ia64_stub.c for gdb
for the public domain.
Seems strange that a google search still only shows myself when I search on the
{ia64 gdb stub} keywords. I'd just like double check and avoid duplicating effort.
HP has an exceptional version of GDB, KWDB, that can do src debugging
over the internet and it appears to have been ported to ia64. Unfortunately,
the stub doesn't appear to be under the GNU copyleft.
-piet
~
next parent reply other threads:[~2002-03-29 6:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EAF7540DFBCCD311BC9900A0C9D4BE610AE2C3@exchange.northwesttechnical.com>
[not found] ` <000101c1d679$724fbde0$1601a8c0@northwesttechnical.com>
[not found] ` <20020329064011.A6198@www.piet.net>
2002-03-28 22:24 ` piet delaney [this message]
2002-03-30 12:41 ` Jim Wilson
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=20020329142309.A8255@www.piet.net \
--to=piet@freebsd.piet.net \
--cc=gdb@sources.redhat.com \
--cc=linux-ia64@linuxia64.org \
--cc=rags@freebsd.piet.net \
--cc=wilson@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