From: Paul Naert <paul.naert@polymtl.ca>
To: gdb@sourceware.org
Subject: [Compile] Inserting compiled code via jumps
Date: Wed, 12 Dec 2018 16:09:00 -0000 [thread overview]
Message-ID: <20181212160933.Horde.zgKx70qWwfqOpGUV4Dq7x5_@www.imp.polymtl.ca> (raw)
Hi,
I am a masters student and I would like to devote my research to
improving GDB's GCC Compile and Execute by adding the possibility to
jump directly to the compiled code without having to hit a breakpoint.
The idea is to reuse the same principle that was used in fast
tracepoints to insert code in a compiled program, except that instead
of jumping to GDB's collector function we would execute the code
compiled by GCC each time we hit the selected instruction.
Given the code for compiling a snippet of C through GCC and the code
for inserting fast tracepoint already exist, I think that this should
be feasible.
What I was wondering is :
- Has someone already worked on this ? On the wiki page there are
mentions to future projects that seem related (fast breakpoint
conditions most notably)
- Do you see any reason why that would not work that I missed,
except for the limitations of the existing Compile project?
Thank you,
Paul NAERT
next reply other threads:[~2018-12-12 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 16:09 Paul Naert [this message]
[not found] ` <87pnu25rkk.fsf@tromey.com>
2018-12-17 17:01 ` Paul Naert
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=20181212160933.Horde.zgKx70qWwfqOpGUV4Dq7x5_@www.imp.polymtl.ca \
--to=paul.naert@polymtl.ca \
--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