From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] change gdbserver's pids to int
Date: Thu, 04 Dec 2008 23:30:00 -0000 [thread overview]
Message-ID: <20081204232923.GA32253@caradoc.them.org> (raw)
In-Reply-To: <e394668d0812041502u2c56ebdei8d28a4af9ee06822@mail.gmail.com>
On Thu, Dec 04, 2008 at 03:02:05PM -0800, Doug Evans wrote:
> > Are you sure that every place you touched gets a system PID, not a
> > thread ID? They used to be ints, but were changed to unsigned long
> > because NPTL's TIDs do not fit in an int.
>
> Ya, I specifically stuck to pids.
A lot of these places used to be thread IDs. At some point we
stopped reporting those to GDB, to avoid the same sort of problem.
> > Also, do Windows PIDs fit in an int? Win32 pids must, but I expect
> > we'll get a Win64 port at some point.
>
> Good question. I was in part going for consistency with what gdb uses.
> Maybe it would be useful to have gdb_pid_t, gdb_tid_t types that both
> gdb and gdbserver use.
I don't personally think consistency between gdb and gdbserver is all
that big of a goal. There's lots of similar code between gdb and
gdbserver, but even if we fixed up common interfaces I think we'd have
to add a lot of gunk to gdbserver to be able to entirely share
anything; we already have some such gunk for signals.c.
Switching them to some typedef to int sounds OK to me. I admit I
don't see the point, but I wouldn't reject the patch. Dumping them
all back to int just makes them less opaque than they are now though.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-12-04 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 1:24 Doug Evans
2008-12-04 13:16 ` Daniel Jacobowitz
2008-12-04 23:02 ` Doug Evans
2008-12-04 23:30 ` Daniel Jacobowitz [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=20081204232923.GA32253@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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