From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Limit attempts to place breakpoints on _start, __start, and main in solib-svr4.c
Date: Tue, 07 Dec 2010 07:41:00 -0000 [thread overview]
Message-ID: <20101207074055.GA1257@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20101203140433.69c17fc4@mesquite.lan>
Hi Kevin,
On Fri, 03 Dec 2010 22:04:33 +0100, Kevin Buettner wrote:
> We do want to (potentially) attempt to place the breakpoints on
> _start, __start, and main in case 1, but not for case 2 and 3.
if this functionality change is enough for now this patch looks safe to me.
> The patch below won't necessarily work correctly with stubs which do
> not implement the qAttached packet. (gdbserver does implement
> qAttached.) My reading of remote.c indicates that stubs which do
> not implement "qAttached" will end up causing attach_flag to be 0.
Therefore it also falls back to the current/safe mode in such case.
> Further comments?
> * solib-svr4.c (enable_break): Don't attempt to place breakpoints,
> when attaching, on the names in bkpt_names: _start, __start, and
> main.
As Mark also agrees with this patch I find it OK for the check-in.
Thanks,
Jan
next prev parent reply other threads:[~2010-12-07 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 23:02 Kevin Buettner
2010-11-30 0:07 ` Jan Kratochvil
2010-11-30 5:15 ` Kevin Buettner
2010-12-01 1:06 ` Kevin Buettner
2010-12-01 23:03 ` Jan Kratochvil
2010-12-03 21:04 ` Kevin Buettner
2010-12-05 19:47 ` Mark Kettenis
2010-12-07 7:41 ` Jan Kratochvil [this message]
2010-12-13 15:47 ` Kevin Buettner
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=20101207074055.GA1257@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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