From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25657 invoked by alias); 10 Dec 2005 01:34:00 -0000 Received: (qmail 25646 invoked by uid 22791); 10 Dec 2005 01:33:59 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 10 Dec 2005 01:33:58 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id jBA1Xuv9028111; Fri, 9 Dec 2005 20:33:56 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id jBA1XoV12068; Fri, 9 Dec 2005 20:33:50 -0500 Received: from [172.16.24.50] (bluegiant.sfbay.redhat.com [172.16.24.50]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id jBA1XmfU029884; Fri, 9 Dec 2005 20:33:49 -0500 Message-ID: <439A307C.3080107@redhat.com> Date: Sat, 10 Dec 2005 09:06:00 -0000 From: Michael Snyder User-Agent: Mozilla Thunderbird (X11/20050322) MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sourceware.org Subject: Re: [RFA] checkpoint / restart, and multi-fork debugging References: <439614B1.2030206@redhat.com> <20051209143700.GB11917@nevyn.them.org> In-Reply-To: <20051209143700.GB11917@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00190.txt.bz2 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). I don't really know about "address space randomization" (though I can guess what it means)...