From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30432 invoked by alias); 5 Aug 2009 18:58:04 -0000 Received: (qmail 30423 invoked by uid 22791); 5 Aug 2009 18:58:03 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 05 Aug 2009 18:57:54 +0000 Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KNX00J002KXQH00@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Wed, 05 Aug 2009 21:57:44 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.149.138]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KNX001F63C6D150@i-mtaout7.012.net.il>; Wed, 05 Aug 2009 21:57:43 +0300 (IDT) Date: Wed, 05 Aug 2009 18:58:00 -0000 From: Eli Zaretskii Subject: Re: [rfc] Infrastructure to disable breakpoints during inferior startup In-reply-to: <200908051814.n75IED4s005139@d12av02.megacenter.de.ibm.com> To: Ulrich Weigand Cc: thiago.bauermann@gmail.com, gdb-patches@sourceware.org, pedro@codesourcery.com, tromey@redhat.com, jkratoch@redhat.com Reply-to: Eli Zaretskii Message-id: <83bpmunl5l.fsf@gnu.org> References: <200908051814.n75IED4s005139@d12av02.megacenter.de.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-08/txt/msg00077.txt.bz2 > Date: Wed, 5 Aug 2009 20:14:13 +0200 (CEST) > From: "Ulrich Weigand" > Cc: thiago.bauermann@gmail.com (Thiago Jung Bauermann), > gdb-patches@sourceware.org, pedro@codesourcery.com, tromey@redhat.com, > jkratoch@redhat.com > > I'll be happy to add documentation to gdbint.texinfo, but I'm not quite > sure where to start. This patch was about handling breakpoints when the > main objfile is relocated during startup. Where does this fit in the > current structure of the manual? A natural place might be a section on > how relocation is handled in general, typically in the context of shared > libraries ... but these topics are not currently covered at all. > > Any suggestions where to start here? You could add a new chapter about relocations and have it include a single section about the issue you were talking about. gdbint.texinfo looks like a car crash anyway (and what's worse, there's a lot of outdated information there), so I wouldn't at this time be worried about form too much, just about the content. TIA