From: Fred Fish <fnf@specifix.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com, fnf@specifix.com
Subject: Re: [RFC] Patch to add kernel threads support for FreeBSD 6.1
Date: Thu, 08 Feb 2007 23:05:00 -0000 [thread overview]
Message-ID: <200702081605.01875.fnf@specifix.com> (raw)
In-Reply-To: <200702082147.l18Ll7NU005756@brahms.sibelius.xs4all.nl>
On Thursday 08 February 2007 14:47, Mark Kettenis wrote:
> Can you avoid introducing supply_xxregset()/fill_xxregset() and use
> register sets instead?
OK.
> Is the child_suppress_run hack really necessary? I thought the right
> stratum was automatically chosen.
It was introduced to work around the issue that you can't have two
targets ready to run at the same time, apparently. That's an area
I'm not intimately familar with. I believe the patch originated in
some BSD code.
> > +#define GET_PID(ptid) ptid_get_pid (ptid)
> > +#define GET_LWP(ptid) ptid_get_lwp (ptid)
> > +#define GET_THREAD(ptid) ptid_get_tid (ptid)
> > +
> > +#define IS_LWP(ptid) (GET_LWP (ptid) != 0)
> > +#define IS_THREAD(ptid) (GET_THREAD (ptid) != 0)
> > +
> > +#define BUILD_LWP(lwp, pid) ptid_build (pid, lwp, 0)
> > +#define BUILD_THREAD(tid, pid) ptid_build (pid, 0, tid)
>
> These days these macros are really pointless and I think they should
> die (here and elsewhere in the code).
Fine by me. :-)
Of course this is somewhat of a moot point if the fact that the main
support file comes directly from FreeBSD prevents this patch from
going into mainline gdb.
-Fred
prev parent reply other threads:[~2007-02-08 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 0:19 Fred Fish
2007-02-08 21:47 ` Mark Kettenis
2007-02-08 23:05 ` Fred Fish [this message]
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=200702081605.01875.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=gdb-patches@sources.redhat.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