From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] new kdb patch with disassembler support
Date: Tue, 13 Jun 2000 15:46:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205133@msgid-missing> (raw)
Hi,
I grew tired of not being able to disassemble code with kdb. This was
really tedious when I was looking at the PAL problems. So I decided
to add support for it. It is included in this patch and is based on
the BFD code.
Summary of changes:
- upgrade to 2.4-test1
- disassembler support via the id command. Symbol lookups is fully
supported. Single stepping now shows code as well. (S.Eranian)
- restructured machine dependent input/output (kdba_io.c). There was
way too much code duplication. A side effect is that with 2 consoles
(serial+vga) you can now debug from either places. (S.Eranian)
- vastly enhanced command line editing (S.Eranian):
* (CTRL-U/CTRL-C)
* history buffer via (CTRL-P/CTRL-N)
* Enter will redo the last command (that's for David!)
- some code cleanups (David + Stephane)
- updated backtracing support to latest unwind code (D.Mosberger)
The patch is relative to 2.4-test1 + David's 0609 diff.
It is available from the HPLabs web site at:
ftp://ftp.hpl.hp.com/pub/linux-ia64/kdb-2.4-test1.patch
Enjoy,
Known Issue:
- on serial line the output of certain editing commands like CTRL-U
is bogus but the buffer is valid. This is due to some timing problems
with the UART which I did not have time to really fix. Anybody with
UART understanding can probably fix this in minutes. Patch welcomed !
-Stephane
reply other threads:[~2000-06-13 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590678205133@msgid-missing \
--to=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.