From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22401 invoked by alias); 22 Jan 2010 13:46:28 -0000 Received: (qmail 22393 invoked by uid 22791); 22 Jan 2010 13:46:28 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Jan 2010 13:46:19 +0000 Received: (qmail 19596 invoked from network); 22 Jan 2010 13:46:17 -0000 Received: from unknown (HELO caradoc.them.org) (dan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Jan 2010 13:46:17 -0000 Date: Fri, 22 Jan 2010 13:46:00 -0000 From: Daniel Jacobowitz To: Paul Koning Cc: Jie Zhang , Michael Snyder , Dave Korn , gdb@sourceware.org Subject: Re: Reset breakpoint after load? Message-ID: <20100122134609.GA6990@caradoc.them.org> Mail-Followup-To: Paul Koning , Jie Zhang , Michael Snyder , Dave Korn , gdb@sourceware.org References: <4B5560E0.3080901@analog.com> <4B582A02.2040501@gmail.com> <4B589CF2.2040304@vmware.com> <20100121211950.GA11880@caradoc.them.org> <4B58D811.8070604@analog.com> <4B5915CB.7090705@analog.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-01/txt/msg00182.txt.bz2 On Fri, Jan 22, 2010 at 06:46:23AM -0500, Paul Koning wrote: > Right, I noticed that it's set that way. I have a GDB with local mods > for our embedded system work; one of the mods is to change the default > to "on". That makes debug much faster and makes sense in any case. > It's very rare to need it to be off. It shouldn't be a global option, anyway, or rather most places should not consult the global option. Maybe the option itself should be tristate (on/off/auto). My hypothesis is that any place which combines code analysis with use of the symbol table - e.g. most unwinders, and prologue skipping - should specify that reads from the executable are OK. If code in the executable self-modifies in such a way as to make that incorrect, then it was going to misbehave anyway. Anyone see a problem with that - or have a suggestion on implementation? -- Daniel Jacobowitz CodeSourcery