From: Stan Shebs <stan@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: How do I patch my binary
Date: Tue, 30 Nov 2010 23:54:00 -0000 [thread overview]
Message-ID: <4CF58E9B.9060401@codesourcery.com> (raw)
In-Reply-To: <4C9D95B9-3EBF-45F3-9B4A-A706D786FD84@elis.ugent.be>
On 11/25/10 6:42 AM, Jonas Maebe wrote:
>
> On 25 Nov 2010, at 15:16, Marc Khouzam wrote:
>
>> Here is the XCode doc about Fix and Continue which explains it nicely
>> for a user:
>> http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/XcodeDebugging/230-Modifying_Running_Code/modifying_running_code.html
>>
>
> Note that in the mean time that functionality has been deprecated by
> Apple, and may even have already been completely removed from the
> latest Xcode releases. It also never worked that well (hence the
> deprecation, I guess).
One of the critical aspects to making it work was that all references
were dynamic and indirected, so that everything could end up in
different locations after the fix and yet still be found when you
resumed execution. But that meant special compiler flags, and more
differences between "development" and "production" code. (I note the
contemporaneous discussion about compiler options for Linux.)
In the generic Linux/ELF/ABI etc context, I think it's going to be even
harder to make it work reliably enough for users to trust. Certainly it
was disappointing at Apple, to have put forth the coordinated effort and
then not seen much uptake.
Stan
next prev parent reply other threads:[~2010-11-30 23:54 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
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 [this message]
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=4CF58E9B.9060401@codesourcery.com \
--to=stan@codesourcery.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