From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA/rs6000-aix] software_single_step gdbarch method no longer set
Date: Tue, 07 Feb 2006 20:03:00 -0000 [thread overview]
Message-ID: <20060207200351.GD1215@adacore.com> (raw)
In-Reply-To: <20051231060032.GA17641@nevyn.them.org>
Hey Daniel,
I am just realizing that I never got around to answering you.
> I have not looked at the patch much (won't this year). However, if
> you're feeling especially motivated, we could sidestep this issue...
> there's a related cleanup I've been meaning to do for a long while.
>
> The software single step method in the gdbarch is always used if it is
> set. But, that doesn't make a lot of sense. The gdbarch method should
> mean "software single step is supported"; the predicate "software
> single step is required" should live in the target vector instead!
> It's a property of the target. e.g. MIPS GNU/Linux doesn't implement
> PTRACE_SINGLESTEP, but if you're connected to a kernel debugging
> session using a hardware ICE, then maybe you've really got hardware
> single step.
Makes sense, but ...
> It's unfortunately a little trickier than that since remote targets
> don't currently report whether using software singlestep is OK :-(
> So setting the default behavior may not be simple. I know gdbserver
> needs some adjustment here.
I don't have that much time in the forseeable future to work on this,
unfortunately. I would also like to work on some other cleanup
activities, including the procfs stuff (which I promised to Mark and
yet haven't had time to look at).
So I'd rather see if my proposal can go in for now.
Thanks,
--
Joel
next parent reply other threads:[~2006-02-07 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051231054133.GL4734@adacore.com>
[not found] ` <20051231060032.GA17641@nevyn.them.org>
2006-02-07 20:03 ` Joel Brobecker [this message]
2006-02-09 17:55 ` Kevin Buettner
2006-02-09 18:00 ` Daniel Jacobowitz
2006-02-10 20:57 ` Joel Brobecker
2006-02-12 7:46 ` Jim Blandy
2006-02-14 20:46 ` Joel Brobecker
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=20060207200351.GD1215@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.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