From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6742 invoked by alias); 17 Jul 2007 15:47:00 -0000 Received: (qmail 6730 invoked by uid 22791); 17 Jul 2007 15:46:59 -0000 X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,FORGED_RCVD_HELO,SPF_HELO_PASS,SPF_PASS 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; Tue, 17 Jul 2007 15:46:55 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l6HFkopN004776; Tue, 17 Jul 2007 11:46:50 -0400 Received: from pobox.hsv.redhat.com (pobox.hsv.redhat.com [172.16.16.12]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l6HFknLV002193; Tue, 17 Jul 2007 11:46:49 -0400 Received: from localhost.localdomain (dhcp-232.hsv.redhat.com [172.16.17.232]) by pobox.hsv.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id l6HFknS3005508; Tue, 17 Jul 2007 11:46:49 -0400 Message-ID: <469CE468.7030006@redhat.com> Date: Tue, 17 Jul 2007 15:47:00 -0000 From: Phil Muldoon User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: Mark Wielaard CC: Roland McGrath , frysk@sourceware.org Subject: Re: Leaving visible breakpoints in memory/core (Was: Breakpoint stepping) References: <20070712024947.9F7354D0489@magilla.localdomain> <4696398B.6040404@redhat.com> <1184601180.3628.53.camel@dijkstra.wildebeest.org> In-Reply-To: <1184601180.3628.53.camel@dijkstra.wildebeest.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00133.txt.bz2 Mark Wielaard wrote: > But if you really wanted to then you could at least get the breakpoints > instructions that frysk-core inserted from BreakpointAddresses (which I > will soon extend with a handy getAllAdresses() method for fixing bug > #4761), and then you can get the actual breakpoint instruction bytes > used from the relevant Isa getBreakpointInstruction(). This is probably > too low level though. And since you cannot guarantee that the created > core file is read back through frysk (someone could be using gdb!) I > don't know where you would actually put this information or how you > would make all consumers know about both the original bytes and the > breakpoint instructions in the image. > What's the argument about just dumping the task's memory as is, with all breakpoints there? A corefile is a representation of that process and it's thread as it is at that time ... And besides, this is only addressing a tiny corner case of someone running fcore on a process that is being debugged with Frysk at that time. I can't think of a scenario why I would do that. Can you? If they were debugging with GDB and fcore was run on that process, the included core image would have all the break point information. It seems like a lot of work for a very small edge case? Regards Phil