From: Ulrich Weigand <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: uweigand@de.ibm.com, manjo@austin.ibm.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Target vectors for native Linux targets
Date: Sun, 21 Aug 2005 15:21:00 -0000 [thread overview]
Message-ID: <200508211328.j7LDSVhH003835@53v30g15.boeblingen.de.ibm.com> (raw)
In-Reply-To: <200508202214.j7KMEC94021466@elgar.sibelius.xs4all.nl> from "Mark Kettenis" at Aug 21, 2005 12:14:12 AM
Mark Kettenis wrote:
> Hmm, it would be preferable to have it the other way around, since
> that would make eliminating the nm-linux.h files, but I can see why
> you did it this way. In the end we might just define USE_LINUX_TARGET
> if GDB_NM_FILE isn't defined. So it's not really important. I've
> added some more comments on the patch inline.
I guess we could make a config/nm-new-linux.h or something -- that
would be a (temporary) new nm file, but would allow to remove the
per-platform Linux nm files as platforms are converted over ...
> > To avoid calling child_xfer_memory I had to switch to using xfer_partial
> > instead. This change also bubbled up to linux-thread-db.c. (But seeing
> > as xfer_memory is deprecated, that's probably a good idea anyway.)
>
> Indeed. When I did conversions in the past the
> depreceated_xfer_memory always came back to haunt me, so we have to be
> a bit careful. Did you test your patch on another Linux target that
> wasn't converted yet?
I tested it on s390 *without* the follow-up patch, and that went
fine as well ...
> > What do you think of this approach?
>
> I think this should be committed. However, since Daniel did some work
> in this area before, I'd like to give him the opportunity to comment.
> Can you keep this patch on the backburner until he's back?
Sure. Thanks for your comments!
> Daniels earlier attempt had linux_target accept a `struct target_ops
> *' as an argument to serve as an alternative for a plain
> inf_ptrace_target(). I thought that was necessary for i386 and sparc
> Linux targets, but I think I've convinced myself that it isn't.
Since you can always override the target functions afterwards,
I'm not sure why this would be necessary ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
Linux on zSeries Development
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2005-08-21 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 18:30 [RFC] GDB patches for hw watchpoints Manoj Iyer
2005-08-17 18:46 ` Eli Zaretskii
2005-08-17 23:03 ` Mark Kettenis
2005-08-19 0:53 ` [RFC/RFA] Target vectors for native Linux targets Ulrich Weigand
2005-08-21 10:48 ` Mark Kettenis
2005-08-21 15:21 ` Ulrich Weigand [this message]
2005-08-21 15:53 ` Mark Kettenis
2005-09-04 15:48 ` Daniel Jacobowitz
2005-09-04 22:48 ` Daniel Jacobowitz
2005-09-05 17:32 ` Ulrich Weigand
2005-09-10 18:13 ` Daniel Jacobowitz
2005-09-11 22:02 ` [committed] s390 watchpoints (Re: [RFC/RFA] Target vectors for native Linux targets) Ulrich Weigand
2005-09-11 23:09 ` Daniel Jacobowitz
2005-09-18 1:20 ` [RFC] GDB patches for hw watchpoints Daniel Jacobowitz
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=200508211328.j7LDSVhH003835@53v30g15.boeblingen.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.com \
--cc=mark.kettenis@xs4all.nl \
/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