From: Daniel Gutson <daniel.gutson@tallertechnologies.com>
To: gdb <gdb@sourceware.org>
Subject: Re: Breakpoint commands compiler
Date: Fri, 17 Oct 2014 16:12:00 -0000 [thread overview]
Message-ID: <CAF5HaEUf+0+Fpy4oGKA9STTCLn4L1aFDBRKH_owhyBkXb8RwwA@mail.gmail.com> (raw)
In-Reply-To: <CAF5HaEVWapj-ZVTshW7aGdjFhmMohZqw9dCezwTrxH__FSEkLg@mail.gmail.com>
On Fri, Oct 17, 2014 at 12:42 PM, Daniel Gutson
<daniel.gutson@tallertechnologies.com> wrote:
> Hi,
>
> gdb is sometimes used for changing the runtime behavior of a program.
> That is, suppose there is a program that has a bug,
> it is spotted with gdb, then I create a set of non-stopping breakpoints that
> "fix" the runtime behavior by altering memory and registers.
> It does work, but it's slow.
>
> I was thinking to start a project to add a "breakpoint commands compiler"
> to gdb, which basically generates C code from the breakpoint commands
> (one function per breakpoint),
> which in turns calls a C API (similar to the python api), invokes the compiler
(Note: I just saw the C API discussion in this list. Funny).
> (user-specified), loads it as a shared object, and finally replaces the commands
> of the breakpoints by calls to the compiled breakpoint-functions.
>
> Any comment/suggestion? Would this be accepted within gdb?
>
> Thanks,
>
> Daniel.
>
> --
>
> Daniel F. Gutson
> Chief Engineering Officer, SPD
>
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
>
> Phone: +54 351 4217888 / +54 351 4218211
>
> Skype: dgutson
--
Daniel F. Gutson
Chief Engineering Officer, SPD
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54 351 4217888 / +54 351 4218211
Skype: dgutson
next prev parent reply other threads:[~2014-10-17 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 15:42 Daniel Gutson
2014-10-17 16:12 ` Daniel Gutson [this message]
2014-10-17 16:57 ` Doug Evans
2014-10-17 17:38 ` Phil Muldoon
2014-10-17 17:39 ` Jan Kratochvil
2014-10-23 15:35 ` David Taylor
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=CAF5HaEUf+0+Fpy4oGKA9STTCLn4L1aFDBRKH_owhyBkXb8RwwA@mail.gmail.com \
--to=daniel.gutson@tallertechnologies.com \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox