From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Baurzhan Ismagulov'" <ibr@radix50.net>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: How do I patch my binary
Date: Wed, 24 Nov 2010 15:01:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC572E759001@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20101123215005.GG5574@radix50.net>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Baurzhan Ismagulov
> Sent: Tuesday, November 23, 2010 4:50 PM
> To: gdb@sourceware.org
> Subject: Re: How do I patch my binary
>
> On Tue, Nov 23, 2010 at 04:31:22PM -0500, Marc Khouzam wrote:
> > My hope was that I could modify the source code (outside of
> GDB), recompile
> > the binary and have GDB load and use the new binary,
> without having to restart
> > the program. I couldn't get this to work (using 'set write
> on' and reloading
> > the new binary).
>
> I don't think you can.
>
> Which platform?
Linux x86.
I'm trying to do with C/C++ the hot-swap that Java allows.
So, if GDB can't do it on its own, can we involve the compiler/linker
to make this happen? Is there more complexity with C/C++ than with Java?
The section below of the doc talks about patching, but doesn't describe
a way to actually do it :-)
http://sourceware.org/gdb/current/onlinedocs/gdb/Patching.html#Patching
Thanks
Marc
next prev parent reply other threads:[~2010-11-24 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 21:31 Marc Khouzam
2010-11-23 21:50 ` Baurzhan Ismagulov
2010-11-24 15:01 ` Marc Khouzam [this message]
2010-11-24 15:15 ` Baurzhan Ismagulov
2010-11-25 10:51 ` Jan Kratochvil
2010-11-25 14:16 ` Marc Khouzam
2010-11-25 14:42 ` Jonas Maebe
2010-11-30 23:54 ` Stan Shebs
2010-11-23 21:53 ` Pedro Alves
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=F7CE05678329534C957159168FA70DEC572E759001@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=ibr@radix50.net \
/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