From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: thiago.bauermann@gmail.com (Thiago Jung Bauermann),
gdb-patches@sourceware.org, pedro@codesourcery.com,
tromey@redhat.com, jkratoch@redhat.com
Subject: Re: [rfc] Infrastructure to disable breakpoints during inferior startup
Date: Wed, 05 Aug 2009 18:14:00 -0000 [thread overview]
Message-ID: <200908051814.n75IED4s005139@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <83zlagoje4.fsf@gnu.org> from "Eli Zaretskii" at Aug 03, 2009 09:13:39 PM
Eli Zaretskii wrote:
> > From: Thiago Jung Bauermann <thiago.bauermann@gmail.com>
> > Date: Mon, 3 Aug 2009 00:08:58 -0300
> > Cc: "Ulrich Weigand" <uweigand@de.ibm.com>, Pedro Alves <pedro@codesourcery.com>, tromey@redhat.com, Jan Kratochvil <jkratoch@redhat.com>
> >
> > But in the long run IMHO we want to start a tradition of creating patches to
> > gdbint.texinfo for this kind of "plumbing" work. :^)
>
> Yes, definitely.
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?
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-08-05 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 17:14 Ulrich Weigand
2009-07-22 20:32 ` Tom Tromey
2009-07-23 15:49 ` Ulrich Weigand
2009-07-23 16:51 ` Tom Tromey
2009-07-23 18:06 ` Ulrich Weigand
2009-07-23 18:57 ` Pedro Alves
2009-07-24 22:49 ` Tom Tromey
2009-07-24 23:32 ` Multi-exec patches (Was: [rfc] Infrastructure to disable breakpoints during inferior startup) Tom Tromey
2009-07-25 16:05 ` Pedro Alves
2009-07-25 19:31 ` Pedro Alves
2009-07-27 17:39 ` Multi-exec patches Tom Tromey
2009-07-27 18:45 ` Tom Tromey
2009-07-28 14:28 ` Pedro Alves
2009-07-29 22:03 ` Tom Tromey
2009-07-31 15:45 ` [rfc] Infrastructure to disable breakpoints during inferior startup Ulrich Weigand
2009-08-03 3:07 ` Thiago Jung Bauermann
2009-08-03 18:13 ` Eli Zaretskii
2009-08-05 18:14 ` Ulrich Weigand [this message]
2009-08-05 18:58 ` Eli Zaretskii
2009-08-06 17:46 ` Tom Tromey
2009-08-06 18:42 ` Eli Zaretskii
2009-08-06 19:12 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908051814.n75IED4s005139@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jkratoch@redhat.com \
--cc=pedro@codesourcery.com \
--cc=thiago.bauermann@gmail.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox