From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Jan Kratochvil'" <jan.kratochvil@redhat.com>
Cc: "'Baurzhan Ismagulov'" <ibr@radix50.net>,
"'gdb@sourceware.org'" <gdb@sourceware.org>
Subject: RE: How do I patch my binary
Date: Thu, 25 Nov 2010 14:16:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC572E759723@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20101125105140.GA2367@host0.dyn.jankratochvil.net>
On Thu, 25 Nov 2010, Jan Kratochvil wrote:
> On Wed, 24 Nov 2010 16:00:39 +0100, Marc Khouzam wrote:
> > 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?
>
> http://www.opensource.apple.com/tarballs/gdb/gdb-1472.tar.gz
> /* APPLE LOCAL fix-and-continue */
> src/gdb/fix-and-continue.c
>
> Howdy from Apple; Fix and Continue implemented Yet Again
> http://sourceware.org/ml/gdb/2003-06/msg00500.html
This is awesome! Thanks Jan!
From the email description, this seems to be exactly what I was looking for.
It allows the user to recompile a program, as any other compilation is done,
and ask GDB to patch it in.
The email mentions that this feature works with the IDE. But it also
gave me the impression that you could edit with emacs/vi, recompile with GCC
from a shell, and then give GDB the 'fix and continue' command. To me, that
fits very well with GDB and would have not outside dependencies.
(Of course, I would add this support in Eclipse, but that is not a requirement
for GDB).
From the email:
"Fix and continue is a feature implemented by many other debuggers:
[...] Sun Workshop, SGI ProDev WorkShop, Microsoft's Visual Studio,
HP's wdb, and Sun's Hotspot Java VM all provide this feature in one way or another"
I don't know enough about GDB to be able to port the feature myself.
I wonder if anyone else in the community would be interested in
porting this feature?
I think this would be a really nice addition to FSF GDB.
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
Thanks
marc
next prev parent reply other threads:[~2010-11-25 14:16 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 [this message]
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=F7CE05678329534C957159168FA70DEC572E759723@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb@sourceware.org \
--cc=ibr@radix50.net \
--cc=jan.kratochvil@redhat.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