Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [RFA] checkpoint / restart, and multi-fork debugging
Date: Tue, 13 Dec 2005 06:17:00 -0000	[thread overview]
Message-ID: <uhd9gd223.fsf@gnu.org> (raw)
In-Reply-To: <439A307C.3080107@redhat.com> (message from Michael Snyder on 	Fri, 09 Dec 2005 17:33:48 -0800)

> Date: Fri, 09 Dec 2005 17:33:48 -0800
> From: Michael Snyder <msnyder@redhat.com>
> CC: gdb-patches@sourceware.org
> 
> Daniel Jacobowitz wrote:
> > On Fri, Dec 09, 2005 at 04:23:34PM +0200, Eli Zaretskii wrote:
> > 
> >>>A nice problem this solves is handling watchpoints when the system has
> >>>address space randomization.  I run into this all the time when
> >>>debugging -- back before this feature was added to the OS I would put
> >>>a fair amount of effort into finding some address to watch in one
> >>>debug session, then restart the inferior with a watchpoint set.
> >>>Randomization made this impossible; but with this patch I could just
> >>>make a checkpoint at 'main'.
> >>
> >>Perhaps we should mention this as well.
> > 
> > Amen!
> 
> Something like this?
> 
>      It may be useful to take a checkpoint at 'main', and return
>      to that checkpoint instead of restarting the program.  This
>      will help keep things deterministic by avoiding random things
>      that may occur during creation of a new process (such as
>      address space randomization).

Yes, except that I'd explicitly mention that some systems, like
GNU/Linux, randomize the address space for security reasons, and that
on such systems it is hard to set a watchpoint or breakpoint on
absolute addresses.  Then the suggested use of this feature will make
more sense, I think.


  parent reply	other threads:[~2005-12-10 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 15:11 Michael Snyder
2005-12-09 14:23 ` Tom Tromey
2005-12-09 19:51   ` Eli Zaretskii
2005-12-09 20:59     ` Daniel Jacobowitz
2005-12-10  9:06       ` Michael Snyder
2005-12-10  9:57         ` Daniel Jacobowitz
2005-12-13  6:17         ` Eli Zaretskii [this message]
2005-12-10  7:24   ` Michael Snyder
2005-12-09 19:36 ` Eli Zaretskii
2005-12-10  8:59   ` Michael Snyder
2005-12-12 23:32     ` Eli Zaretskii

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=uhd9gd223.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@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