From: "McQueen, Brian" <Brian.McQueen@schwab.com>
Subject: New Project - gdb
Date: Tue, 28 Sep 2004 15:47:21 -0700 [thread overview]
Message-ID: <72796EB188CDD411A7BF0002A52CAC1623FBFB18@n1026smx.nt.schwab.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
I just thought of an interesting guile project, which I will never do
myself. But its interesting enough that someone else might want to do it.
Add guile to gdb so the debugger and all of its fancy features can be
accessed and driven via scheme. I think it goes along with the notion of
guile being an extension language in a sense in that the debugger can be
attached to executables, and so scheme can be used to extend/drive
executables through this guile/gdb tool - if your vendor won't give you the
source code which is my problem. It might not work or be the least bit
practical, but it sounds like a very fun and educational project.
[-- Attachment #1.2: Type: text/html, Size: 1006 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2004-09-28 22:47 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72796EB188CDD411A7BF0002A52CAC1623FBFB18@n1026smx.nt.schwab.com \
--to=brian.mcqueen@schwab.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).