From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26981 invoked by alias); 7 Feb 2002 19:44:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26884 invoked from network); 7 Feb 2002 19:43:59 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 7 Feb 2002 19:43:59 -0000 Received: from redhat.com (notinuse.cygnus.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id LAA16784; Thu, 7 Feb 2002 11:43:57 -0800 (PST) Message-ID: <3C62D749.6371EDD9@redhat.com> Date: Thu, 07 Feb 2002 11:44:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Jim Blandy CC: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Improved support for overlay breakpoints in ROM References: <200202050011.g150BfB21148@reddwarf.cygnus.com> <3C608108.C7BA0407@redhat.com> Content-Type: multipart/mixed; boundary="------------5576DE91D00FE13168018034" X-SW-Source: 2002-02/txt/msg00194.txt.bz2 This is a multi-part message in MIME format. --------------5576DE91D00FE13168018034 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-length: 862 Jim Blandy wrote: > > Michael Snyder writes: > > > Jim Blandy wrote: > > > > > > Typo: > > > > > > > + /* On the same principal, an overlay manager can arrange to call a > > > > > > s/principal/principle/ > > > > > > It seems to me that, if overlay management is disabled, or set to > > > `manual', we shouldn't even set a breakpoint in _ovly_debug_event. > > > > By analogy with the longjmp breakpoint, it seems easiest just to > > create the breakpoint when the symbol file is loaded, and then > > enable/disable it as needed. When it is disabled, it doesn't > > represent any significant overhead. > > Okay, I see. > > > > We need to document the new rules in the GDB manual. > > > > Yep. > > ... How can we prevent this from falling through the cracks? I don't > mind doing it, but I'm afraid I'm going to forget. How's this? --------------5576DE91D00FE13168018034 Content-Type: text/plain; charset=us-ascii; name="ovly.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ovly.patch" Content-length: 1265 2002-02-06 Michael Snyder * gdb.texinfo (overlays): Mention new magic symbol '_ovly_debug_event', which allows GDB to keep better track of overlays. Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.85 diff -p -r1.85 gdb.texinfo *** gdb.texinfo 2002/02/01 18:41:51 1.85 --- gdb.texinfo 2002/02/06 18:27:16 *************** executable file. When @value{GDBN} find *** 6646,6651 **** --- 6646,6660 ---- the entry's @code{mapped} member to determine whether the overlay is currently mapped. + In addition, your overlay manager may define a function called + @var{_ovly_debug_event}. If this function is defined, @value{GDBN} + will silently set a breakpoint there. If the overlay manager then + calls this function whenever it has changed the overlay table, this + will enable @value{GDBN} to accurately keep track of which overlays + are in program memory, and update any breakpoints that may be set + in overlays. This will allow breakpoints to work even if the + overlays are kept in ROM or other non-writable memory while they + are not being executed. @node Overlay Sample Program @section Overlay Sample Program --------------5576DE91D00FE13168018034--